I had a crash...stack seemed to be damaged. The debugger did not show a proper stack, just a hexadecimal number.
No function names nothing..
I took me half day to figure out that stack was not damaged.. just there was a unhandled exception.
I started Sysinternals process explorer which showed a readable stack for any thread I looked it. The process explorer can show snapshots of the stack. If the debugger could show the current state of the stack, that would be an improvement.
Is it not a bug in the debugger? if the process explorer can show a correct stack.. Why cannot the debugger?
So it can be a bug.
A.
I assume you are referring to ide-internal debugger for VC++. Well, there are certainly things to improve.
Anyway, have you tried to switch the thread? Often the win32 reports different thread to us than what is really the one with problem... Some threads do not have symbolic info.