Hmm..... Ok, I have seen this type of unexplained behavior in the past and appears to be something with the debugger getting triggered on a phantom address. Never have been able to prove it as it hard to duplicate. So first can you do the following, build with optimization level 0, if you aren't already. This provides the best debugging experience and see if the problem still occurs. If so, when halted, open the "View disassembly" window and take a snap shot and share with me.
↧