| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Studio 12.3: Debugging a Program With dbx Oracle Solaris Studio 12.3 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris Studio 12.3: Debugging a Program With dbx Oracle Solaris Studio 12.3 Information Library |
4. Viewing and Navigating To Code
5. Controlling Program Execution
6. Setting Breakpoints and Traces
8. Evaluating and Displaying Data
11. Debugging Multithreaded Applications
Changing the Default Signal Lists
Trapping the FPE Signal (Solaris Platforms Only)
Determining Where the Exception Occurred
Determining the Cause of the Exception
Automatically Handling Signals
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
The dbx cont command supports the -sig signal option, which lets you resume execution of a program with the program behaving as if it had received the system signal signal.
For example, if a program has an interrupt handler for SIGINT (^C), you can type ^C to stop the application and return control to dbx. If you issue a cont command by itself to continue program execution, the interrupt handler never executes. To execute the interrupt handler, send the signal, SIGINT, to the program:
(dbx) cont -sig int
The step command, next command, and detach command accept -sig as well.
|