Function, Entry, Method, or Procedure Breakpoint dialog box

Restriction: This dialog box is not available when debugging on the AS/400.

The name and behavior of this dialog box change depending on the language of the program you are debugging and the platform on which that program is running. The dialog box is available when debugging on the AIX, Solaris, OS/390, and Windows NT operating systems.

This page contains specific information for the dialog box that is appropriate for the following combinations of program language and platform:

The table below describes the push buttons that appear in all variations of this dialog box. The names of control groups and subgroups appear in italics, and control names appear in bold.

Push buttons
OK Creates a method breakpoint using the settings you specified, then closes this dialog box.
Set Creates the method breakpoint using the settings you specified, but keeps the 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 this dialog box without creating a new breakpoint.
Help Displays this help panel.

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

Use the Function Breakpoint dialog box to set a new breakpoint that stops program execution when the start of a function is encountered or redefine existing function breakpoints. You can also specify the executable and source files where you want to set the breakpoint.

ngcpp.gif (261 bytes) If the function you specify is an overloaded C++ function (your program contains two or more functions with the same name but different signatures), an Available Functions dialog box appears, displaying a list of the overloads of the function. Choose the desired one from the list.

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.
Executable Optional. Select the executable to which the breakpoint applies from the program names in this selection list. Otherwise, enter a new executable name.
Object Optional. Select the object file to which the breakpoint applies from the object file names in this selection list. Otherwise, enter a new object file name.
Function Select the function to which the breakpoint applies from the function names in this selection list. Otherwise, enter a new function name.
Defer breakpoint Select this check box if you want to set a function breakpoint in a program module that is not currently loaded.

If you enter an incorrect source file, function, or program unit, the Debugger is not able to activate the breakpoint when the executable is loaded, and the breakpoint remains 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.

ngcpp.gif (261 bytes) If you set a deferred function breakpoint on a C++ function, and that function is overloaded, the Debugger sets the breakpoint in all of the overloaded functions when the executable is loaded. When an executable in which you have set a deferred breakpoint is loaded, the breakpoint state changes from deferred to active. When the executable is freed, the breakpoint state changes back to deferred.

Debugging information only Select this check box if you only want to load source code for programs that have debugging information.
Case sensitive If checked, entry fields are character case sensitive.
Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose what threads to set the breakpoint in. To select a thread ID from the list, highlight the thread where 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 you want the Debugger to stop on. 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)

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

ng390.gif (283 bytes) Function Breakpoint dialog box

Use the Function Breakpoint dialog box to set a new breakpoint that stops program execution when the start of a function or program unit is encountered. You can also specify the executable and source files 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 Use controls in this group to define where the breakpoint is placed in the program being debugged.
Executable Optional. Select the executable to which the breakpoint applies from the program names in this selection list. Otherwise, enter a new executable name.
Object Optional. Select the object file to which the breakpoint applies from the object file names in this selection list. Otherwise, enter a new object file name.
Function Select the function to which the breakpoint applies from the function names in this selection list. Otherwise, enter a new function name.
Defer breakpoint Select this check box if you want to set a function breakpoint in a program module that is not currently loaded.

If you enter an incorrect source file, function, or program unit, the Debugger is not able to activate the breakpoint when the executable is loaded, and the breakpoint remains 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.

Debugging information only Select this check box if you only want to load source code for programs that have debugging information.
Case sensitive If checked, entry fields are character case sensitive.
Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose what threads to set the breakpoint in. To select a thread ID from the list, highlight the thread where 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 you want the Debugger to stop on. 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)

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

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

Use the Entry Breakpoint dialog box to set a new breakpoint that stops program execution when an entry point is encountered or redefine existing entry breakpoints. You can also specify the executable and source files 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 Use controls in this group to define where the breakpoint is placed in the program being debugged.
Executable Optional. Select the executable to which the breakpoint applies from the program names in this selection list. Otherwise, enter a new executable name.
Object Optional. Select the object file to which the breakpoint applies from the object file names in this selection list. Otherwise, enter a new object file name.
Entry Point Select the entry point to which the breakpoint applies from the entry point names in this selection list. Otherwise, enter a new entry point name.
Defer breakpoint Select this check box if you want to set an entry breakpoint in a program module that is not currently loaded.

If you enter an incorrect source file, entry point, or program unit, the Debugger is not able to activate the breakpoint when the executable is loaded, and the breakpoint remains 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.

Debugging information only Select this check box if you only want to load source code for programs that have debugging information.
Case sensitive If checked, entry fields are character case sensitive.
Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose what threads to set the breakpoint in. To select a thread ID from the list, highlight the thread where 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 you want the Debugger to stop on. 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.

ngwin.gif (301 bytes) Entry Breakpoint dialog box

Use the Entry Breakpoint dialog box to set a new breakpoint that stops program execution when the a specific entry point is encountered. You can also specify the executable and source and listing files 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 Use controls in this group to define where the breakpoint is placed in the program being debugged.
Executable Optional. Select the executable to which the breakpoint applies from the program names in this selection list. Otherwise, enter a new executable name.
Object Optional. Select the object file to which the breakpoint applies from the object file names in this selection list. Otherwise, enter a new object file name.
Entry Point Select the entry point to which the breakpoint applies from the entry point names in this selection list. Otherwise, enter a new entry point name.
Defer breakpoint Select this check box if you want to set an entry breakpoint in a program module that is not currently loaded.

If you enter an incorrect source file, entry point, or executable, the Debugger is not able to activate the breakpoint when the executable is loaded, and the breakpoint remains 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.

Debugging information only Select this check box if you only want to load source code for programs that have debugging information.
Case sensitive If checked, entry fields are character case sensitive.
Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose what threads to set the breakpoint in. To select a thread ID from the list, highlight the thread where 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 you want the Debugger to stop on. 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".

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

Use the Method Breakpoint dialog box to set a new breakpoint that stops program execution when the method is
reached or redefine existing method breakpoints. If the method you specify is an overloaded method (a class contains two or more methods with the same name but different signatures), an Available Methods dialog box appears, from which you can select the desired method from a list of the overloaded methods.

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.
Package Optional. Select the package to which the breakpoint applies from the selection list of packages. Otherwise, enter a new package name.
Class Optional. Select the class to which the breakpoint applies from the selection list of classes. Otherwise, enter a new class name.
Method Select the method to which the breakpoint applies from the method names in this selection list. Otherwise, enter a new method name.
Defer breakpoint Select this check box if you want to set a method breakpoint in a program module that is not currently loaded.

When a class in which you have set a deferred breakpoint is loaded, the state of the breakpoint changes from deferred to active. When the class is unloaded, the breakpoint state changes back to deferred. If you enter an
incorrect package, class, or method, the Debugger will not be able to activate the breakpoint when the class is loaded, and the breakpoint remains in the deferred state. If you set a deferred method breakpoint on an overloaded method, the Debugger sets the breakpoint in all of the overloaded methods when the class is loaded.

Debugging information only Select this check box if you want to set the breakpoint only if the method contains debugging information.
Case sensitive If checked, entry fields are character case-sensitive.
Optional Parameters Provide additional control over when breakpoints are triggered.
Expression You can enter an expression into this field. Program execution stops at the breakpoint only if the condition specified in this field evaluates to true.

Procedure Breakpoint dialog box

Use the Procedure Breakpoint dialog box to set a new breakpoint that stops program execution when the start of a procedure is encountered or redefine existing procedure breakpoints. You can also specify the executable and source files 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 Use controls in this group to define where the breakpoint is placed in the program being debugged.
Executable Optional. Select the executable to which the breakpoint applies from the program names in this selection list. Otherwise, enter a new executable name.
Object Optional. Select the object file to which the breakpoint applies from the object file names in this selection list. Otherwise, enter a new object file name.
Procedure Select the function to which the breakpoint applies from the procedure names in this selection list. Otherwise, enter a new procedure name.
Defer breakpoint Select this check box if you want to set a procedure breakpoint in a program module that is not currently loaded.

If you enter an incorrect source file, procedure, or executable, the Debugger is not able to activate the breakpoint when the executable is loaded, and the breakpoint remains 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.

Debugging information only Select this check box if you only want to load source code for programs that have debugging information.
Case sensitive If checked, entry fields are character case sensitive.
Optional Parameters Provide additional control over when breakpoints are triggered.
Thread This selection list lets you choose what threads to set the breakpoint in. To select a thread ID from the list, highlight the thread where 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 you want the Debugger to stop on. 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 Fortran program you could type the following:

log_var

where log_var is the name of a logical variable.

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