Progress
Debugger Guide


Managing Breakpoints

You can set and remove breakpoints in any procedure, whether or not it is the current procedure, and whether or not the procedure currently exists. A breakpoint is identified by both the procedure name and line number in the debug listing (not the source listing) where the breakpoint occurs. Note that a breakpoint occurs on a physical line (not a statement) in the procedure. If you want the procedure to break on a particular statement, you must ensure that the statement is the first statement on the line where you set the breakpoint.

NOTE: There are certain user-interface triggers where the Debugger ordinarily ignores all breakpoints. The Debugger cannot take control in these triggers without competing with the window system for the mouse pointer—an effect that, if allowed to happen, causes a deadlock in the window system. Instead, the Debugger displays a message indicating that it cannot take control there. Debugging these triggers requires alternative techniques. For more information, see the "Debugging Events" section in this chapter.

You can manage breakpoints using the commands listed in Table 5–1.

Table 5–1: Breakpoint Management Commands 
Function
Command
Set a single breakpoint.
BREAK1
Remove one or more specified breakpoints.
CANCEL BREAK
Remove all breakpoints.
CANCEL ALL
Display all current breakpoints in the data panel.
SHOW BREAKS
  1. The Break option of the Debug menu also invokes the BREAK command.


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