Click above to get retro games delivered to your door ever month!

If you are using the non-GUI version of the debugger, switch focus to the
debugger screen and press CTRL-BREAK.

If you are using the GUI-based version of the debugger or one of the remote
debug servers, switch focus to the debugger or debug server screen and click
anywhere.  When you switch to the debugger screen, you will see a pop-up
stating that:


     The debugger cannot be used while the application is
     running.  Do you want to interrupt the application?

If you select "Yes", the debugger will attempt to interrupt the application.
 If you select "No", the debugger will resume waiting for the application to
hit a breakpoint or terminate.

If you select "Yes" and the debugger cannot interrupt the application, you
can click on the debugger again and it will display a pop-up asking:


     The debugger could not sucessfully interrupt your
     application.  Do you want to terminate the application?

If you select "Yes", the debugger will terminate your application.  If you
select "No", the debugger will resume waiting for the program to hit a
breakpoint or terminate.

Note:
    Under Windows 95, it is very difficult to interrupt a program that is in
    an infinite loop or spending most of its time in system API's.  Under
    Windows 95, you can only interrupt a program that is responding to
    messages (or looping in its own thread code).  If your program is an
    infinite loop, interrupting the program will likely fail.  The only
    option in this case is to terminate the program.

    This is not an issue under Windows NT which has a superior debug API.

If you press CTRL-BREAK when the application has focus, you will terminate
the application being debugged rather than interrupting it.