bafter (Simulink Reference)

Insert a breakpoint after a specified method

Syntax

bafter
bafter m:mid
bafter <sid:bid | gcb> [mth] [tid:TID]
bafter <s:sid | gcs> [mth] [tid:TID]
bafter mdl [mth] [tid:TID]

Arguments

mid
method ID

sid:bid
block ID

gcb
currently selected block

sid
system ID

gcs
currently selected system

mdl
currently selected model

mth
a method name, e.g., Outputs.Major

TID
task ID

`mid`	method ID
`sid:bid`	block ID
`gcb`	currently selected block
`sid`	system ID
gcs	currently selected system
`mdl`	currently selected model
mth	a method name, e.g., `Outputs.Major`
TID	task ID

Description

bafter inserts a breakpoint after the current method.

bafter m:mid inserts a breakpoint after the method specified by mid (see Method ID).

bafter sid:bid inserts a breakpoint after each invocation of the method of the block specified by sid:bid (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. To break at invocation of a block's methods in minor time steps, execute minor before or after executing this form of the bafter command.

bafter s:sid inserts a breakpoint after each method of the root system or nonvirtual subsystem specified by the system ID: sid.

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 mdl 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.

See Also

break, ebreak, tbreak, xbreak, nanbreak, zcbreak, rbreak, clear, where, slist, systems

atrace break