Not just yet. :\ If I run out of other avenues of investigation, I will.
I noticed just now that my command-line debug was actually two debug sessions, nested. I'm installing the x86 symbols now to see if they remedy that; it seems like something that would definitely throw C::B through a loop.
Okay, so this is very strange. CDB is debugging ITSELF, debugging my executable, when I start it on the command line. Is this normal?
And installing the symbol package removed the errors, but did not fix the unresponsive debug terminal.
Some more info:
- I'm using a custom compiler/debugger config for MSVC 2010, as it was not among the available options initially.
- When I close Code::Blocks to halt the debugging, it displays an "unable to stop the debug process!" dialog, twice.
EDIT: Out of ideas; I'll try out that nightly build...