Function Breakpoint dialog box
The behavior of the Function Breakpoint dialog box changes depending on the platform
running the program you are debugging. This dialog box is not available when debugging on
the AS/400. Select the appropriate platform:

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.
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 Overloaded 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 |
Select the executable to which the breakpoint will apply from the
programs names in this selection list. Otherwise enter a new executable name. |
Source |
Select the source file to which the breakpoint will apply from the source
file names in this selection list. Otherwise enter a new source file name. |
Function |
Select the function to which the breakpoint will apply 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 will not be able to activate the breakpoint when
the executable 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.
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 a
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. The execution of the program
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)
Variables in a conditional expression that is associated with a function breakpoint are
limited to any static or global variables known to the called function when the function
is called. The expression cannot contain local or automatic variables. |
|
Push-buttons |
OK |
Creates the function breakpoint using the settings you specified, then
closes the Function Breakpoint dialog box. |
Set |
Creates the function breakpoint using the settings you specified, but
keeps the Function 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 Function Breakpoint dialog box without creating a new
breakpoint. |
Help |
Displays this help panel. |
|
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 |
Select the executable to which the breakpoint will apply from the
programs names in this selection list. Otherwise enter a new executable name. |
Source |
Select the source file to which the breakpoint will apply from the source
file names in this selection list. Otherwise enter a new source file name. |
Function |
Select the function to which the breakpoint will apply 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 will not be able to activate the breakpoint when
the executable 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. |
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. The execution of the program
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 function breakpoint using the settings you specified, then
closes the Function Breakpoint dialog box. |
Set |
Creates the function breakpoint using the settings you specified, but
keeps the Function 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 Function Breakpoint dialog box without creating a new
breakpoint. |
Help |
Displays this help panel. |
|
