User`s guide

Managing Breakpoints, Traces, and Conditional Commands

Listing Breakpoints, Traces, and Conditional Commands

The status command lists all of the breakpoints, traces, and conditional

commands that you have set and indicates whether they are enabled or

disabled.

For example, consider executing the following commands while debugging

a program called test:

(dbx) stop in foo

Process 0: [3] stop in foo

(dbx) r

Process 22631 (test) started

[3] Process 22631 (test) stopped at [foo:38 ,0x10001050]

38 r = foo2(i+1);

(dbx) trace total

Process 22631: [4] trace total in foo

(dbx) when at 60 {print i,j }

Process 22631: [5] when at “/usr/var/tmp/dbx_examples/

test.c”:60 { print i, j }

If you enter status, you see the following:

(dbx) status

Process 22631: [3] stop in foo

Process 22631: [4] trace total in foo

Process 22631: [5] when at “/usr/var/tmp/dbx_examples/

test.c”:60 { print i, j }

Disabling Breakpoints, Traces, and Conditional

Commands

The disable command allows you to temporarily disable a breakpoint, trace,

or conditional command so that it is inoperative and has no effect on

program execution. dbx remembers all information about a disabled

breakpoint, trace, or conditional command, and you may enable it using the

enable command described in “Enabling Breakpoints, Traces, and

Conditional Commands” on page 72.