Progress
Debugger Guide


Terminating an Application from the Debugger

The QUIT and STOP commands, when executed, immediately terminate the running application. In general, the QUIT command terminates in exactly the same way as the 4GL QUIT statement, and the STOP command terminates in exactly the same way as the 4GL STOP statement. In other words, the QUIT command completes the active transaction, and the STOP command backs it out.

Unwinding the Procedure Call Stack

If you started the running application from the Debugger using the RUN command, both the QUIT and STOP commands terminate the application, returning control to the Debugger. You must enter additional QUIT or STOP commands for each additional application on the procedure call stack you want to terminate. If the Debugger is running in application mode and the initial application is next on the stack, the initial application terminates and returns to its startup environment. If the initial application is a startup (-p) procedure and the Debugger is running in application mode using the DEBUGGER system handle, entering the STOP command restarts the startup procedure (unless the STOP is trapped by an ON STOP statement). If the Debugger is running in stand-alone mode from the operating system (-debug), entering the STOP command returns control to the Debugger.

NOTE: Any application you start from the Debugger returns to the Debugger, whether you terminate it from within the application or with the Debugger QUIT or STOP command.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095