| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Studio 12.2: Debugging a Program With dbx |
4. Viewing and Navigating To Code
5. Controlling Program Execution
6. Setting Breakpoints and Traces
8. Evaluating and Displaying Data
11. Debugging Multithreaded Applications
16. Debugging Fortran Using dbx
17. Debugging a Java Application With dbx
18. Debugging at the Machine-Instruction Level
19. Using dbx With the Korn Shell
20. Debugging Shared Libraries
The stop command sets a source-level breakpoint.
The stop command has the following general syntax:
stop event_specification [modifier]
When the specified event occurs, the process is stopped.
The following specific syntaxes are some of the more important syntaxes that are valid in native mode. For additional events, see Setting Event Specifications.
Stop execution now. Only valid within the body of a when command.
Stop execution now but do not update the Oracle Solaris Studio IDE Debugger windows.
Stop execution when the memory specified by address_expression has been accessed. See also Stopping Execution When an Address Is Accessed.
Stop execution at line_number. See also Setting a stop Breakpoint at a Line of Source Code.
Stop execution when the value of variable has changed.
Stop execution when the condition denoted by condition_expression evaluates to true.
Stop execution when function is called. See also Setting a stop Breakpoint in a Function.
C++ only: Set breakpoints on all member functions of a class, struct, union, or template class. -norecurse is the default. If -recurse is specified, the base classes are included. See also Setting Breakpoints in All Member Functions of a Class.
Stop execution when any function in file_name is called.
C++ only: Set breakpoints on all non-member functions name.
C++ only: set breakpoints on all member functions name. See Setting Breakpoints in Member Functions of Different Classes.
C++ only: set breakpoint on entry into any non-static method of the class and all its base classes when called from the object object_expression. -recurse is the default. If -norecurse is specified, the base classes are not included. See also Setting Breakpoints in Objects.
line_number is the number of a source code line.
function is the name of a function.
class_name is the name of a C++ class, struct, union, or template class.
mode specifies how the memory was accessed. It can be composed of one or all of the letters:
The memory at the specified address has been read.
The memory has been written to.
The memory has been executed.
mode can also contain the following:
Stops the process after the access (default).
Stops the process before the access.
name is the name of a C++ function.
object_expression identifies a C++ object.
variable is the name of a variable.
The following modifiers are valid in native mode.
The specified event occurs only when condition_expression evaluates to true.
Execution stops only if the specified event occurs during the extent of function.
Starting at 0, each time the event occurs, the counter is incremented. When number is reached, execution stops and the counter is reset to 0.
Starting at 0, each time the event occurs, the counter is incremented. Execution is not stopped.
Create a temporary breakpoint that is deleted when the event occurs.
Create the breakpoint in a disabled state.
Do instruction level variation. For example, step becomes instruction level stepping, and at takes a text address for an argument instead of a line number.
Make this event permanent across debug. Certain events (like breakpoints) are not appropriate to be made permanent. delete all will not delete permanent handlers, use delete hid.
Hide the event from the status command. Some import modules may choose to use this. Use status -h to see them.
Execution stops only if the specified event occurs in the given LWP.
Execution stops only if the specified event occurs in the given thread.
The following specific syntaxes are valid in Java mode.
Stop execution when the memory specified by class_name.field_name has been accessed.
Stop execution at line_number.
Stop execution at line_number in file_name.
Stop execution when the value of field_name in class_name has changed.
Stop execution when any class is loaded.
Stop execution when class_name is loaded.
Stop execution when any class is unloaded.
Stop execution when class_name is unloaded.
Stop execution when the condition denoted by condition_expression evaluates to true.
Stop execution when class_name.method_name has been entered, and the first line is about to be executed. If no parameters are specified and the method is overloaded, a list of methods is displayed.
Stop execution when class_name.method_name has been entered, and the first line is about to be executed.
Set breakpoints on all non-member methods class_name.method_name.
Set breakpoints on all non-member methods class_name.method_name.
Stop execution when a Java exception has been thrown.
Stop execution when a Java exception of type has been thrown.
where:
class_name is the name of a Java class, using either the package path (using period (.) as a qualifier; for example, test1.extra.T1.Inner) or the full path name (preceded by a pound sign (#) and using slash (/) and dollar sign ($) as qualifiers; for example, #test1/extra/T1$Inner). Enclose class_name in quotation marks if you use the $ qualifier.
condition_expression can be any expression, but it must evaluate to an integral type.
field_name is the name of a field in the class.
file_name is the name of a file.
line_number is the number of a source code line.
method_name is the name of a Java method.
mode specifies how the memory was accessed. It can be composed of one or all of the letters:
The memory at the specified address has been read.
The memory has been written to.
mode can also contain the following:
Stops the process before the access.
The program counter will point at the offending instruction.
parameters are the method’s parameters.
type is a type of Java exception. -unhandled or -unexpected can be used for type.
The following modifiers are valid in Java mode:
The specified event occurs only when condition_expression evaluates to true.
Starting at 0, each time the event occurs, the counter is incremented. When number is reached, execution stops and the counter is reset to 0.
Starting at 0, each time the event occurs, the counter is incremented. Execution is not stopped.
Create a temporary breakpoint that is deleted when the event occurs.
Create the breakpoint in a disabled state.
See also stopi Command for setting a machine-level breakpoint.
For a list and the syntax of all events see Setting Event Specifications.
|