Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Studio 12.3: Debugging a Program With dbx Oracle Solaris Studio 12.3 Information Library |
Debugging a Core File in the Same Operating Environment
If Your Core File Is Truncated
Debugging a Mismatched Core File
Eliminating Shared Library Problems
Mapping the Compile-time Directory to the Debug-time Directory
Setting dbx Environment Variables
Creating Your Own dbx Commands
Compiling a Program for Debugging
Creating a Separate Debug File
Code Compiled Without the -g Option
Shared Libraries Require the -g Option for Full dbx Support
Killing a Program Without Terminating the Session
Saving and Restoring a Debugging Run
Saving a Series of Debugging Runs as Checkpoints
Saving and Restoring Using replay
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
You can attach a running process to dbx using the process ID as an argument to the dbx command or the dbxtool command.
$ dbx program_name process_id
or
dbxtool program_name process_id
To attach dbx to a running process that includes Java code and C JNI (Java Native Interface) code or C++ JNI code:
$ dbx program_name{.class | .jar} process_id
You can also attach to a process using its process ID without knowing the name of the program.
$ dbx - process_id
or
$ dbxtool - process_id
Because the program name remains unknown to dbx, you cannot pass arguments to the process in a run command.
For more information, see Attaching dbx to a Running Process.