System Debug Reference Manual (32650-90888)

Chapter 4 95

System Debug Command Speciﬁcations :-Exit

$nmdebug > cm

%cmdebug > bd 2

deleted: NM [2] TRANS 48.0000a610 SEG':?PROCESSSTUDENT

CM Ref count = 0

deleted: CM [2] PROG % 0.1665 ?PROCESSSTUDENT

Delete CM breakpoint number 2. The corresponding NM breakpoint is also deleted.

%cmdebug > bd 3

deleted: NM [3] TRANS 48.0000a66c SEG':PROCESSSTUDENT+%265

CM Ref count = 1

deleted: CM [3] PROG % 0.1672 PROCESSSTUDENT+%265

Delete CM breakpoint number 3. In this example, two CM breakpoints are mapped to one

NM breakpoint (indicated by the reference counter). The corresponding NM breakpoint

has its CM reference count decremented by one. When the reference count is zero, the NM

breakpoint is deleted.

%cmdebug > bl

CM [4] PROG % 0.1673 PROCESSSTUDENT+%266 SEG' (CSTX 1)

Corresponding NM bp = 3

%cmdebug > nm

$nmdebug > bl

NM [3] TRANS 48.0000a66c SEG':PROCESSSTUDENT+%265

CM Ref count = 1

NM [4] TRANS 20.0000b940 FSEG:?FREAD

count: 0/64 cmdlist: {wl "Read another 100 records";c}

CM Ref count = 1

List the remaining CM and NM breakpoints.

Limitations, Restrictions

If breakpoints are listed for a process other than the current PIN, Debug has no knowledge

of the procedure names associated with the addresses unless the speciﬁed process is

running the exact same program ﬁle.

Debug only

Breakpoint list. Lists breakpoint entries, speciﬁed by index number.

Syntax

BL [

number

| @ [:

| @] ]

The BL command is used to list process-local and global (system-wide) breakpoints. Global

breakpoints are always displayed after the process-local breakpoints. Users without

privileged mode (PM) capability are shown only the list of process-local breakpoints. Users