bafter
Insert breakpoint after specified method
Syntax
bafter ba bafter m:mid
bafter <(taskIdx
)sysIdx
:blkIdx
| gcb> [mth
] [tid:TID
] bafter <s:sysIdx
| gcs> [mth
] [tid:TID
] bafter model [mth
] [tid:TID
] bafter modelName <(taskIdx)sysIdx
:blkIdx
| gcb> [mth
] [tid:TID
]
Arguments
| Method ID |
| Task ID |
| Block ID |
| Currently selected block |
| System ID |
gcs | Currently selected system |
| Currently selected model |
mth | A method name, e.g.,
|
TID | Task ID |
modelName | The name of the referenced model within the hierarchy of the top model, which is under debugging. |
Description
bafter
inserts a breakpoint after the current method.
Instead of bafter
, you can use the short form of
ba
with any of the syntaxes.
bafter
m
:
mid
inserts a breakpoint
after the method specified by mid
(see “Method ID”).
bafter
(taskIdx)
sysIdx
:
blkIdx
inserts a breakpoint after each invocation of the method of the block specified by
sysIdx
:
blkIdx
(see “Block ID”)
in major time steps. bafter gcb
inserts a breakpoint after each
invocation of a method of the currently selected block (see gcb
) in major times steps.
bafter
s:
sysIdx
inserts a breakpoint after each
method of the root system or nonvirtual subsystem specified by the system ID:
sysIdx
.
Note
The systems
command displays the
system IDs for all nonvirtual systems in the currently selected model.
bafter
gcs
inserts a breakpoint
after each method of the currently selected nonvirtual system.
bafter
model
inserts a breakpoint
after each method of the currently selected model.
The optional mth
parameter allow you to set a breakpoint
after a particular block, system, or model method and task. For example, bafter
gcb
Outputs
sets a
breakpoint after the Outputs method of the currently selected block.
The optional TID parameter allows you to set a breakpoint after invocation of a method
by a particular task. For example, suppose that the currently selected nonvirtual
subsystem operates on task 2 and 3. Then bafter
gcs
Outputs
tid:
2
sets a breakpoint after the invocation of the
subsystem's Outputs method that occurs when task 2 is active.