Printable View
strange behavier during debuging.
class xxx
{
...
private a;
private b;
private function()
{
...
b = false;
...
}
...
}
I searched the whole project for variable a and put a break point at each place. then when I debut and step through the "b=false;", the value of a got changed in the watch window. I mean just before the statement, a is empty and right after the statement a got some value. program never break else where.
can anybody explain?
Sounds like you overrite 'a' from somwhere in your code.
Since you didn't provide enouph information about your class xxx member variables/methods, nor showed your actual code there is impossible to answer you more... :sick:
1) You are running a different executable than the one you believe you're debugging (i.e. the source code does not match what you're actually running).Quote:
Originally Posted by tangjun
OR
2) You have optimizations turned on. Since optimizations can eliminate or move code around, your source code does not match what the final optimized code would perform.
OR
3) Your code has a serious bug.
Those are three of your possibilities.
Regards,
Paul McKenzie
Add one more to it (since actual code is not provided) :
a is a reference to b.
Paul's point make some sence, I will try explore a little bit, although I don't believe that's the reason.
for all others, I'v pointed out that I searched all my project where a is ever get assigned/modified, and I am sure I covered everything, and those break point never got reached during that call.
BTW, this is c# code.
post the project and we can stop guessing on what might be the cause.
not possible, this is a 800MB project.
1. If the option "Rebuild All" exists for the c# - try it.
2. Try to remove parts of the project until this strange behaviour goes away - then try to understand what could cause this...
Victor,
Does "a" become the value of "b"? Or just some random value?
-Greg Dolley
Why are you asking me? :confused:Quote:
Originally Posted by greg_dolley
Ask OP! :cool:
a has no relationship whatsoever with b.
Have you tried my suggestions from yesterday?
It sounds like memory is getting trounced.
Put a breakpoint on the MEMORY for A, not the variable A. Put the condition on the break point, whenever it changes.
Whenever any code, anywhere, alters that memory, the compiler will stop on it and you can see where its all happening.
Would you mind showing a cut down version of the code that depicts this behaviour? Without that, it no more than you are asking us to blind-guess.Quote:
Originally Posted by tangjun
Oh! Sorry Victor, my mistake. :blush:Quote:
Originally Posted by VictorN
Greg Dolley