| 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 debug command lists or changes the program being debugged. In native mode, it loads the specified application and begins debugging the application. In Java mode, it loads the specified Java application, checks for the existence of the class file, and begins debugging the application.
Print the name and arguments of the program being debugged.
Begin debugging program_name with no process or core.
Begin debugging program_name with core file core.
Begin debugging program_name with process ID process_id.
Begin debugging program with core file core. program_name may be -. dbx will attempt to extract the name of the executable from the core file. For details, see Debugging a Core File.
Begin debugging program_name with process ID process_id. program_name may be -; dbx finds it using /proc.
Force loading of a core file, even if it doesn’t match.
The -r option causes dbx to retain all display, trace, when, and stop commands. With no -r option, an implicit delete all andundisplay O are performed.
The -clone option causes another dbx process to begin execution, permitting debugging of more than one process at a time. Valid only if running in the Oracle Solaris Studio IDE.
Starts another dbx process debugging nothing. Valid only if running in the Oracle Solaris Studio IDE.
Start debugging program_name, even if program_name begins with a dash.
where:
core is the name of a core file.
options are the options listed inOptions.
pid is the process ID of a running process.
program_name is the path name of the program.
Leaks checking and access checking are turned off when a program is loaded with the debug command. You can enable them with the check command (see check Command).
Print the name and arguments of the program being debugged.
Begin debugging program_name with no process.
Begin debugging program_name with process ID process_id.
Begin debugging program_name with process ID process_id. program_name may be -; dbx finds it using /proc
The -r option causes dbx to retain all watch commands, display commands, trace commands, when commands, andstop commands. With no -r option, an implicitdelete all command and undisplay 0 command are performed.
The -clone option causes another dbx process to begin execution, permitting debugging of more than one process at a time. Valid only if running in the Oracle Solaris Studio IDE.
Starts another dbx process debugging nothing. Valid only if running in the Oracle Solaris Studio IDE.
Start debugging program_name, even if program_name begins with a dash.
where:
file_name is the name of a file.
options are the options listed inOptions.
process_id is the process ID of a running process.
program_name is the path name of the program.
Execute commands before prompting for input.
Used with -s, removes
Echo input commands.
Add directory_name to pathmap set (see pathmap Command.
Save and restore keyboard translation state.
Suppress messages about reading stabs.
Run program; if program exits normally, then exit.
Print the readme file for dbx.
Use file instead of current_directory/.dbxrc or $HOME/.dbxrc as the startup file
Suppress reading of initialization file /installation_directory/lib/dbxrc.
Print the version of dbx.
Skip n frames on where command.
Marks the end of the option list; use this if the program name starts with a dash.
|