Line Breakpoint dialog box

The behavior of the Line Breakpoint dialog box changes depending on the platform running the program you are debugging. Select the appropriate platform:

ngaix.gif (307 bytes)ngwin.gif (301 bytes) Line Breakpoint dialog box

Use the Line Breakpoint dialog box to set a new breakpoint on a specific line or to redefine an existing line breakpoint. You can also specify the executable and the source file where you want to set the breakpoint.

Controls and control groupings are described below, as follows:

Group and subgroup names appear in italics, and control names appear in bold.

Table 1. Controls and control groupings for debugging compiled languages.

Required Parameters Use controls in this group to define where the breakpoint is placed in the program being debugged.
Executable Select the executable to which the breakpoint will apply from the program names in this selection list. Otherwise, enter a new executable name.
Object Select the object file to which the breakpoint will apply from the object file names in this selection list. Otherwise, enter a new object file name.
Source (optional) If the source code consists of several files (that is, if one or more files include other files), you can select which source file the breakpoint should be set in from this selection list. Otherwise, enter a new include file name.
Line Enter a number into this field to identify the line where the breakpoint will go within the specified source file.
Defer breakpoint Select this check box if you want to set a line breakpoint in a program module that is not currently loaded.

If you enter an incorrect executable, source, or object file, the Debugger will not be able to activate the breakpoint when the program is loaded, and the breakpoint will remain in the deferred state.

Note: You cannot set a deferred breakpoint in a preloaded executable, but you can set one in a program that has some preloaded executables and some dynamically loaded ones.

Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose which threads to set the breakpoint in. To select a thread ID from the list, highlight the thread in which you want to set the breakpoint. This list is available only on platforms that support multithreaded programs.
Frequency Use the Frequency controls to tell the Debugger when to stop on a breakpoint and when to skip it. The Debugger keeps track of how many times each breakpoint is encountered. The fields in this section tell the Debugger on which encounter of a breakpoint the Debugger should first stop, how often it should stop, and on which encounter the Debugger should no longer stop.
From Enter the first breakpoint encounter on which you want the Debugger to stop. For example, if you want the Debugger to skip over the breakpoint the first five times it is encountered, enter "6".
To Enter the last breakpoint encounter you want the Debugger to stop on. For example, if you want it to start ignoring the breakpoint after the 20th encounter, enter "20". To have it always stop on the breakpoint, enter "Infinity".
Every Enter the frequency with which you want the Debugger to stop on the breakpoint. For example, if you want it to stop on only one out of every four it encounters, enter "4".
Expression You can type an expression into this field. Program execution stops at the breakpoint only if the condition specified in this field tests true.

For example, if you are debugging a C++ program, you could type the following:

(i==1) || (j==k) && (k!=5)

Push buttons
OK Creates the line breakpoint using the settings you specified, then closes the Line Breakpoint dialog box.
Set Creates the line breakpoint using the settings you specified, but keeps the Line Breakpoint dialog box open so you can create more breakpoints.
Default Saves the settings in the Optional Parameters group for use as default settings when you next set a new breakpoint.
Cancel Closes the Line Breakpoint dialog box without creating a new breakpoint.
Help Displays this help panel.


Table 2. Controls and control groupings for interpreted Java debugging.

Required Parameters Use controls in this group to define where the breakpoint is placed in the program being debugged.
Package Select the package to which the breakpoint will apply from the program names in this selection list. Otherwise, enter a new package name.
Class Select the class to which the breakpoint will apply from the class names in this selection list. Otherwise, enter a new class name.
Source (optional) Select from the selection pulldown menu the source file in which the breakpoint should be set. Otherwise, enter a new source file name. When the defer breakpoint check box is selected, the source file name is no longer optional, and the parenthetical word optional disappears from the label.
Line Enter a number into this field to identify the line where the breakpoint will go within the specified source file.
Defer breakpoint Select this check box if you want to set a line breakpoint in a class that is not currently loaded.

If you enter an incorrect package, class, or source file, the Debugger will not be able to activate the breakpoint when the program is loaded, and the breakpoint will remain in the deferred state.

Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose which threads to set the breakpoint in. To select a thread ID from the list, highlight the thread in which you want to set the breakpoint. This list is available only on platforms that support multithreaded programs.
Frequency Use the Frequency controls to tell the Debugger when to stop on a breakpoint and when to skip it. The Debugger keeps track of how many times each breakpoint is encountered. The fields in this section tell the Debugger on which encounter of a breakpoint the Debugger should first stop, how often it should stop, and on which encounter the Debugger should no longer stop.
From Enter the first breakpoint encounter on which you want the Debugger to stop. For example, if you want the Debugger to skip over the breakpoint the first five times it is encountered, enter "6".
To Enter the last breakpoint encounter you want the Debugger to stop on. For example, if you want it to start ignoring the breakpoint after the 20th encounter, enter "20". To have it always stop on the breakpoint, enter "Infinity".
Every Enter the frequency with which you want the Debugger to stop on the breakpoint. For example, if you want it to stop on only one out of every four it encounters, enter "4".
Expression You can type an expression into this field. Program execution stops at the breakpoint only if the condition specified in this field tests true.

For example, if you are debugging a C++ program, you could type the following:

(i==1) || (j==k) && (k!=5)

Push buttons
OK Creates the line breakpoint using the settings you specified, then closes the Line Breakpoint dialog box.
Set Creates the line breakpoint using the settings you specified, but keeps the Line Breakpoint dialog box open so you can create more breakpoints.
Default Saves the settings in the Optional Parameters group for use as default settings when you next set a new breakpoint.
Cancel Closes the Line Breakpoint dialog box without creating a new breakpoint.
Help Displays this help panel.

ngos400.gif (278 bytes) Line Breakpoint dialog box

Use the Line Breakpoint dialog box to set a new breakpoint on a specific line or to redefine an existing breakpoint. You can also specify the executable and source file where you want to set the breakpoint.

This dialog box is invoked when you select Set Breakpoint, Set Line, Set Line Breakpoint, or Modify Breakpoint menu items. You can set a new breakpoint only when this dialog box is invoked by selecting Set Breakpoint, Set Line, or Set Line Breakpoint menu items. You can modify a breakpoint only when this dialog box is invoked by selecting a Modify Breakpoint menu item.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Required Parameters Use controls in this group to define where the breakpoint is placed in the program being debugged.
Program Select the AS/400 program to which the breakpoint will apply from the program names in this selection list. Otherwise, enter a new program name.
Module Select the module to which the breakpoint will apply from the module names in this selection list. Otherwise, enter a new module name.
Source If the source code consists of several files (that is, if one or more files include other files), you can select which source file the breakpoint should be set in from this selection list. Otherwise, enter a new include file name.
Line Enter a number into this field to identify the line where the breakpoint will go within the specified source file.
Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose which threads to set the breakpoint in. To select a thread ID from the list, highlight the thread in which you want to set the breakpoint. This list is available only on platforms that support multithreaded programs.
Frequency Use the Frequency controls to tell the Debugger when to stop on a breakpoint and when to skip it. The Debugger keeps track of how many times each breakpoint is encountered. The fields in this section tell the Debugger on which encounter of a breakpoint the Debugger should first stop, how often it should stop, and on which encounter the Debugger should no longer stop.
From Enter the first breakpoint encounter on which you want the Debugger to stop. For example, if you want the Debugger to skip over the breakpoint the first five times it is encountered, enter "6".
To Enter the last breakpoint encounter you want the Debugger to stop on. For example, if you want it to start ignoring the breakpoint after the 20th encounter, enter "20". To have it always stop on the breakpoint, enter "Infinity".
Every Enter the frequency with which you want the Debugger to stop on this breakpoint. For example, if you want it to stop on only one out of every four it encounters, enter "4".
Expression You can type an expression into this field. Program execution stops at the breakpoint only if the condition specified in this field tests true.

For example, if you are debugging a C++ program, you could type the following:

(i==1) || (j==k) && (k!=5)

Push buttons
OK Creates the line breakpoint using the settings you specified, then closes the Line Breakpoint dialog box.
Set Creates the line breakpoint using the settings you specified, but keeps the Line Breakpoint dialog box open so you can create more breakpoints.
Default Resets the values in the Optional Parameters group to system-supplied defaults.
Cancel Closes the Line Breakpoint dialog box without creating a new breakpoint.
Help Displays this help panel.

ng390.gif (283 bytes) Line Breakpoint dialog box

Use the Line Breakpoint dialog box to set a new breakpoint on a specific line. You can also specify the executable and source or listing file where you want to set the breakpoint.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Required Parameters Define where the breakpoint is placed in the program being debugged.
Executable Select the executable to which the breakpoint will apply from the program names in this selection list. Otherwise, enter a new executable name.
Object Select the object file to which the breakpoint will apply from the object file names in this selection list. Otherwise, enter a new object file name.
Source (optional) If the source code consists of several files (that is, if one or more files include other files), you can select which source file the breakpoint should be set in from this selection list. Otherwise, enter a new include file name.
Line Enter a number into this field to identify the line where the breakpoint will go within the specified source file.
Defer breakpoint Select this check box if you want to set a line breakpoint in a program module that is not currently loaded.

If you enter an incorrect executable, source or file, the Debugger will not be able to activate the breakpoint when the program is loaded, and the breakpoint will remain in the deferred state.

Note: You cannot set a deferred breakpoint in a preloaded executable, but you can set one in a program that has some preloaded executables and some dynamically loaded ones.

Optional Parameters Provide additional control over when breakpoints are triggered.

ngjava.gif (312 bytes) Optional parameters are not available when debugging interpreted Java programs.

Thread This selection list lets you choose which threads to set the breakpoint in. To select a thread ID from the list, highlight the thread in which you want to set the breakpoint. This list is available only on platforms that support multithreaded programs.
Frequency Use the Frequency controls to tell the Debugger when to stop on a breakpoint and when to skip it. The Debugger keeps track of how many times each breakpoint is encountered. The fields in this section tell the Debugger on which encounter of a breakpoint the Debugger should first stop, how often it should stop, and on which encounter the Debugger should no longer stop.
From Enter the first breakpoint encounter on which you want the Debugger to stop. For example, if you want the Debugger to skip over the breakpoint the first five times it is encountered, enter "6".
To Enter the last breakpoint encounter you want the Debugger to stop on. For example, if you want it to start ignoring the breakpoint after the 20th encounter, enter "20". To have it always stop on the breakpoint, enter "Infinity".
Every Enter the frequency with which you want the Debugger to stop on this breakpoint. For example, if you want it to stop on only one out of every four it encounters, enter "4".
Expression You can type an expression into this field. Program execution stops at the breakpoint only if the condition specified in this field tests true.

For example, if you are debugging a C++ program you could type the following:

(i==1) || (j==k) && (k!=5)

ngcobol.gif (330 bytes) Note: Expressions are not supported when debugging COBOL on OS/390.

Note: Variables in a conditional expression associated with a line breakpoint must be static or global variables known to the called function. The expression cannot contain local or automatic variables.

Push buttons
OK Creates the line breakpoint using the settings you specified, then closes the Line Breakpoint dialog box.
Set Creates the line breakpoint using the settings you specified, but keeps the Line Breakpoint dialog box open so you can create more breakpoints.
Default Saves the settings in the Optional Parameters group for use as default settings when you next set a new breakpoint.
Cancel Closes the Line Breakpoint dialog box without creating a new breakpoint.
Help Displays this help panel.