HP 3000 Manuals HP 3000 Manuals
BL
Debug only
Breakpoint list. Lists breakpoint entries, specified by index number.
Syntax
BL [number | @ [: pin | @] ]
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 without PM
capability may only specify PINs that are descendant processes (any
generation) of the current PIN.
Parameters
number The index number of the breakpoint entry to display.
The symbol "@" can be used to display all entries. If
omitted, then all entries are displayed.
pin The PIN for the process whose breakpoint entries are to
be displayed. Typically this is omitted, and pin
defaults to the current process.
The character "@" can be used to indicate global
breakpoint(s).
Refer to appendix C for a discussion of CM object code translation, node
points, and breakpoints in translated CM code.
Examples
$nmdebug > bl
NM [1] PROG 115.00006a8c PROGRAM+$270
NM [2] PROG 115.00006a90 PROGRAM+$274
NM [3] PROG 115.00005d24 processstudent
cmdlist: {wl "Processing #" r26:"d";c}
NM T[4] PROG 115.00005b50 processstudent.highscore
NM [5] GRP 118.00015c88 average
NM [6] GRP 118.00015c8c average+$4
NM [7] GRP 118.00015c90 average+$8
NM [8] USER f4.0012f2b8 p_heap:P_INIT_HEAP
NM [9] USER f4.001f9188 U_INIT_TRAPS
NM |10| SYS a.0074aa34 FREAD
[QUIET] count: 0/64 cmdlist: {wl "Read another 100 records";c}
NM [11] PROG $115.00006984 initstudentrecord+14
NM @[1] SYS a.00668684 trap_handler
[QUIET] cmdlist: {trace ,ism}
Display all breakpoints. Process-local breakpoints are always displayed
first, followed by all global breakpoints. See the Conventions page for
a description of breakpoint notation.
$nmdebug > bl 3
NM [3] PROG 115.00005d24 processstudent
cmdlist: {wl "Processing #" r26:"d";c}
Display process-local breakpoint number 3.
$nmdebug > bl :@
NM @[1] SYS a.00668684 trap_handler
[QUIET] cmdlist: {trace ,ism}
List all of the global breakpoints.
Translated Code Examples
%cmdebug > bl
CM [1] GRP % 0.13 ?AVERAGE SEG' (CST 112)
Corresponding NM bp = 1
CM [2] PROG % 0.1665 ?PROCESSSTUDENT SEG' (CSTX 1)
Corresponding NM bp = 2
CM [3] PROG % 0.1672 PROCESSSTUDENT+%265 SEG' (CSTX 1)
Corresponding NM bp = 3
CM [4] PROG % 0.1673 PROCESSSTUDENT+%266 SEG' (CSTX 1)
Corresponding NM bp = 3
%cmdebug > nm
$nmdebug > bl
NM [1] TRANS 3d.0016962c SEG':?AVERAGE
CM Ref count = 1
NM [2] TRANS 48.0000a610 SEG':?PROCESSSTUDENT
CM Ref count = 1
NM [3] TRANS 48.0000a66c SEG':PROCESSSTUDENT+%265
CM Ref count = 2
NM [4] TRANS 20.0000b940 FSEG:?FREAD
count: 0/64 cmdlist: {wl "Read another 100 records";c}
CM Ref count = 1
Show all of the CM and NM breakpoints. Notice that the CM breakpoints
all have corresponding NM breakpoints. The NM breakpoints show a counter
reflecting the number of corresponding CM breakpoints. However, the list
of corresponding CM breakpoint numbers is not part of the NM breakpoint
listing.
Limitations, Restrictions
If breakpoints are listed for a process other than the current process,
Debug has no knowledge of the procedure names associated with the
addresses unless the specified process is running the exact same program
file.
CAUTION The output format of all System Debug commands is subject to
change without notice. Programs that are developed to
postprocess System Debug output should not depend on the exact
format (spacing, alignment, number of lines, uppercase or
lowercase, or spelling) of any System Debug command output.