JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Studio 12.3: Debugging a Program With dbx     Oracle Solaris Studio 12.3 Information Library
search filter icon
search icon

Document Information


1.  Getting Started With dbx

2.  Starting dbx

3.  Customizing dbx

4.  Viewing and Navigating To Code

5.  Controlling Program Execution

6.  Setting Breakpoints and Traces

7.  Using the Call Stack

8.  Evaluating and Displaying Data

9.  Using Runtime Checking

10.  Fixing and Continuing

11.  Debugging Multithreaded Applications

12.  Debugging Child Processes

13.  Debugging OpenMP Programs

14.  Working With Signals

Understanding Signal Events

Catching Signals

Changing the Default Signal Lists

Trapping the FPE Signal (Solaris Platforms Only)

Determining Where the Exception Occurred

Determining the Cause of the Exception

Sending a Signal to a Program

Automatically Handling Signals

15.  Debugging C++ With dbx

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

A.  Modifying a Program State

B.  Event Management

C.  Macros

D.  Command Reference


Understanding Signal Events

When a signal is to be delivered to a process that is being debugged, the signal is redirected to dbx by the kernel. When this happens, you usually receive a prompt. You then have two choices:

Figure 14-1 Intercepting and Cancelling the SIGINT Signal

image:Diagram of the normal case where the signal is delivered and the debugging case where the signal is intercepted and cancelled by dbx.

In addition, if a certain signal is received frequently, you can arrange for dbx to forward the signal automatically because you do not want it displayed:

ignore signal # “ignore”

However, the signal is still forwarded to the process. A default set of signals is automatically forwarded in this manner (see ignore Command).