Native Inspect Manual (H06.13+, J06.03+)

break (tbreak) Command
The break command sets an instruction breakpoint for the current process, at a specified line,
function, or address. The tbreak command is similar, but sets a temporary breakpoint that is
deleted after it is hit.
Related Commands: Use the enable command (see enable Command (page 78)) and disable
command (see disable Command (page 75)) to enable and disable breakpoints, respectively.
{break|tbreak} [locspec] [flags] [-e llce | if cond-exp]
Where:
locspec
The location at which you want to set a breakpoint. See Syntax of locspec (page 59).
flags
Either or both of the following:
-g
Indicates a global breakpoint, which can be set only by the super ID user after issuing the
priv command. See priv Command (page 108).
-h
Indicates a halt loop breakpoint, which can be set only by the super ID user after issuing
the priv command. See priv Command (page 108).
llce
A low-level conditional expression (cannot be specified with the -h flag). See Syntax of llce
(page 61).
cond-exp
A language expression that produces an integer or Boolean result.
For COBOL-specific considerations, see Evaluating Expressions (page 53).
Setting Conditional Breakpoints
You can set a conditional breakpoint with the break or tbreak command by including either an
llce (a low-level conditional expression, which is evaluated by the breakpoint interrupt handler)
or a source language expression (evaluated by the debugger). In either case, the breakpoint is
reported only if the expression evaluates to True or a nonzero result. Otherwise, execution of the
program continues. For information about specifying llce, see Syntax of llce (page 61).
You can also use the condition Command to associate a condition with a previously set breakpoint.
Setting Global Breakpoints
Global breakpoints are breakpoints that are set using the -g option. Setting global breakpoints
has the following constraints:
• You must be logged on as the super ID.
• You must turn on privileged mode by using the priv command. (See priv Command
(page 108).)
• The operation is exclusive. No other user can perform global debugging at the same time.
A global breakpoint is triggered by any process that executes the code on which the global
breakpoint is set.
NOTE: Set global breakpoints when debugging a problem in code that is shared by multiple
processes. However, use global breakpoints with care because they might result in numerous
processes being suspended in the debugger.
break (tbreak) Command 67