In This Book

Setting Intercepts

Intercepts are like breakpoints that are set on signals and other events. For example, when a signal event occurs, target program execution stops, and a message is displayed indicating whic h signal was generated. Execution stops before the signal is delivered to the target program.

By default, the debugger sets intercepts all HP-UX signals. It also sets, then suspends, intercepts on image loading and unloading, certain thread events, and exit events. In C++ programs, you can also set intercepts on catch and throw events.

Using the Intercepts Dialog Box

The Intercepts dialog box allows you to view and modify intercepts. Invoke it by selecting Execution:Signals/Intercepts . The dialog box in Figure 3-8 appears.

From the Intercepts dialog box, you can:

1.View the current status of all available intercepts.

This list shows all the attributes of each intercept, and also shows the monitor number and the number of times the intercept has been received.

The monitor number does not correspond to the HP-UX signal number. See Appendix C for more information on signal numbers.

2.Temporarily disable or re-activate selected intercepts.

3.Control whether or not messages appear when an intercept occurs.

4.Temporarily disable or re-activate all intercepts.

5.Specify how many times an intercept should be ignored before the debugger handles it.

6.Specify debugger commands to execute when an in tercept occurs.

3-18 Using Monitors (Breakpoints, Watchpoints, Traces, and Intercepts)