> Unfortunately, if I could catch it changing the value by entering such
> a line, I could simply put a breakpoint on that line like this:
>
> if ( (DWORD)&rsThreadData == 0x00000001)
> dwDummy = 0 ; <== breakpoint here.
If the data is static, in the sense that it doesn't change its place in the
memory during execution, the easiest way would be specifying its address (or
should I say the hardest, because you'd have to do it everytime you want to
start debugging.)
Or if it's a member of an object, fully reference it using the object's
name.
What does the debugger complain when you try to set this breakpoint? I
remember once I had this problem in which the debugger just didn't know what
I was talking about when I just specified the variable's name.
> But I suspect the value is being corrupted during the process of
> making the call (since it's not hitting the breakpoint before the call
> is made, but is corrupt when it tries to use it the first time curing
> that call), leaving me nowhere to put such code {:v(
>
> I wonder if I have a special condition where another part of the comms
> receive thread is trying to use that structure at the same time?
> Hmmm...
We'll see. See my other email.
-------------
Ehsan Akhgari
Farda Technology (http://www.farda-tech.com/)
List Owner: [email protected]
[ Email: [EMAIL PROTECTED] ]
[ WWW: http://www.beginthread.com/Ehsan ]
Every deep thinker is more afraid of being understood than of being
misunderstood. The latter perhaps wounds his vanity, but the former wounds
his heart, his sympathy, which always says: "Ah, why would you also have as
hard a time of it as I have?"
-Beyond Good And Evil, F. W. Nietzsche
_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for
subscription changes, and list archive.
