Here is a bug report for console projects. This happens on a 32bit Windows 7 computer. It happens in the debugger branch too and it existed in previous revisions (bug is not new to 6608). A sample project with source is attached.
1) Throw an exception in c++ while running the code in CodeBlocks (not while debugging). Let it be unhandled.
2) Windows will report that the application has crashed and will offer to close the application or search for a solution. Choose to close now.
3) The console will now prompt to "Press any key to continue". Do not press a key.
4) Click 'Abort' in CodeBlocks.
5) Now the process will stay stuck in CodeBlocks. Even though the application has closed, the debugging does not stop. If you click on 'Abort' in CodeBlocks, nothing happens. You also cannot debug/continue anymore since the debugger is already running, but you cannot stop it. Only solution is to kill cb_console_runner.exe in task manager or restart CodeBlocks.
Here is another list of events that trigger the same bug:
1) Throw an exception in c++. Let it be unhandled.
2) Windows will report that the application has crashed. Do nothing here.
3) Click 'Abort' in CodeBlocks.
4) Back to the Windows dialog. Choose to close the program.
5) cb_console_runner.exe is stuck again.
Here is an order of events that does work well:
1) Throw an exception in c++. Let it be unhandled.
2) Windows will report that the application has crashed. Choose to close now.
3) The console will now prompt to "Press any key to continue". Press a key.
4) Everything works fine as expected.
[attachment deleted by admin]