HP 3000 Manuals HP 3000 Manuals
BREAK SET
Sets a breakpoint at the specified location.
Syntax
{BREAK SET} {p-code_offset [,segment] [,system]} [,count] [,{cmdlist}]
{BS } {system }
Parameters
p-code_offset The p-code offset corresponding to the Transact
instruction at which you want to stop program execution.
The range of valid p-code offsets is 0 to 16383. If the
specified p-code offset does not match an actual p-code
value, then the next smaller actual p-code will be used.
segment The segment number corresponding to the instruction
location. The range of valid segments is 0 to 125. The
default is the current segment.
system A string representing the name of the system in which
you want to set the breakpoint. If you only specify
this parameter, a breakpoint is set at the beginning of
the system. Do this if you want to stop at the
beginning of a child system. The default is the current
system.
count A number indicating to the program to stop at the
breakpoint every n times it is reached. For example, to
stop at a breakpoint every third time the p-code offset
is executed, you would specify 3 for count. The range
of count is 1 to 1,000,000. The default is 1.
cmdlst A set of commands executed every time the breakpoint is
reached. This parameter must consist of valid TRANDEBUG
commands separated by semicolons and cannot be NMDEBUG
commands. For example, {AUTORPT;STEP;;;;MODIFY STATUS
-15;CONTINUE}. (Each of the semicolons following STEP
acts like a carriage return if AUTORPT is turned on.)
The cmdlst parameter can be up to 80 characters long.
Discussion
This command lets you set a breakpoint at a specified segment number and
p-code offset within a Transact/iX program. By default, the segment
number is the current segment, so you do not need to specify the location
if it resides in the current segment. The system name parameter does not
have to be specified if the location resides in the system that is
currently executing. If you want to set a breakpoint at the beginning of
a system to be called from the current system, just specify the system
name. If the breakpoint is set successfully, a message is displayed
showing information about the breakpoint.
The range of valid breakpoints is 0 to 63. A maximum of 64 breakpoints
can be set with the BREAK SET command. A combined total of up to 64
additional breakpoints can be set with the DATA BREAK REGISTER and DATA
BREAK SET commands.
Examples
The following examples illustrate setting breakpoints in TRANDEBUG.
TRANDEBUG> break set 24
BREAKPOINT SET:
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
1. CHILD 0 24 1
TRANDEBUG> break set 28,1
BREAKPOINT SET:
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
2. CHILD 1 28 1
TRANDEBUG> break set 10,,PARENT
BREAKPOINT SET:
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
3. PARENT 0 10 1
TRANDEBUG> break set 20,,,3,{DISPLAY MATCH}
BREAKPOINT SET:
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
1. PARENT 0 20 3
CMD LIST>>>>> DISPLAY MATCH
TRANDEBUG> continue
BREAKPOINT ENCOUNTERED, EXECUTION STOPPED:
SYSTEM SEGMENT OFFSET
------------------------------------
PARENT 0 20
EXECUTING BREAKPOINT CMDLIST: DISPLAY MATCH;
MATCH REGISTER:
ITEM1 EQ : 123 AND
ITEM2 EQ : ABC OR
ITEM2 EQ : DEF
TRANDEBUG> break set 10,,myprog
BREAKPOINT SET:
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
0. MYPROG 0 10 1
TRANDEBUG> bs 3,1, myprog,,{DISPLAY MATCH}
BREAKPOINT SET:
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
1. MYPROG 1 3 1
CMD LIST>>>>> DISPLAY MATCH
TRANDEBUG> bs 183,5,,6
SYSTEM SEGMENT OFFSET COUNT
--------------------------------
2. MYPROG 5 183 6