2009-10-06 00:01:01 UTC
RTM. The problem occurs only when debugging an x86 executable (native C++).
I can set breakpoints, and the debugger stops at the breakpoint as expected.
If I press F5, the code executes without any problems. However, if I single
step from the breakpoint (either F10 or F11), I get an access violation
exception (0xC0000005: Access violation reading location 0xNN, where NN
points to unallocated memory). The exception occurs regardless of the
instruction at the IP (i.e. even if it's an instruction that doesn't access
memory), so it's apparently caused by the debugger while placing the single
I've noticed that the problem occurs only *after* a window has been created
in the process. I can single step through the startup code without any
problems, but if I display a message box (or create my application window),
then any single stepping immediately triggers the exception. I can reproduce
the problem consistently in multiple existing projects.
I've applied SP1, and I believe all the remote debugger patches are applied.
What's going on?