Breakpoints
See Also
A breakpoint is a location in a program where an event occurs.
The location where the event occurs is typically a source location.
But not all breakpoints are location based; some are based on
signals, system calls,and changes in data.
The default action when the breakpoint event occurs is to stop
execution until another debugging command is issued. When your program stops on a
breakpoint, you can perform actions like examining the value of
variables and single-stepping through your program.
dbxtool enables you to set several types of breakpoints in C
C++, or Fortran applications using the New Breakpoint dialog. You
can also set line breakpoints directly in the Source Editor.
Breakpoints can be set for the following events:
- File:Line. Program execution stops when the specified line of
source code is about to be executed.
- Function. By default, program execution stops at the
beginning of the first source line in the function. You can specify that
program execution stops on return from the function.
- Class/Method. Program execution stops at the
beginning of the first source line in all member functions in a class
or in a specific member function in all classes.
- Access. By default, program execution stops before the
specified address is accessed. You can specify that you want program execution
to stop after the address is accessed. You can also specify that you
want program execution to stop before or after the address is read from,
written to, or executed.
- Condition. Program execution stops at the line after the line
that caused the condition to evaluate to true.
- C++ Object. Program execution stops when a non-static member
function is called. You can specify that you do not want
breakpoints set on inherited non-static member functions
- Timer. Program execution stops when the program has been
executing the specified number of seconds.
- Signal. By default, program execution stops when the specified signal
is first delivered to the program you are debugging. If you specify a
subcode, program execution stops when the specified signal is first
delivered to the child process of the program.
- Exception. By default, program execution stops when any exception is
thrown. You can specify that you want program execution to stop only when an
uncaught exception or when an unexpected exception is thrown.
- Fault. Program execution stops when the specified fault is
intercepted.
- System Call. Program execution stops when the process
enters or returns from the system call.
- Load Object. Program execution stops when a loadobject
is loaded or when it is unloaded.
- Instruction. Program execution stops when the specified
address is reached.
- Variable. Program execution stops when the value of the
variable changes.
- Process. Program execution stops when the
specified process event occurs.
- Debugger. Program execution stops when the specified debugge
event occurs.
Annotation |
Description |
 | Breakpoint |
 | Disabled breakpoint |
 | Multiple breakpoints |
 | Conditional breakpoint |
 | Disabled conditional breakpoint |
 | Program counter |
 |
Program counter and one breakpoint |
 |
Program counter and multiple breakpoints |
 | The call site or place in the source code from which
the current call on the call stack was made |
- Except for line breakpoints, all breakpoints are defined globally
and therefore affect all IDE projects that include the source on which
a breakpoint is set.
Legal Notices