Main Content

bafter

Insert breakpoint after specified method in simulation debugging session

Description

bafter inserts a breakpoint after the current method.

Note

This function is supported only for simulation debugging sessions started programmatically using the sldebug function or using the sim function with the 'debug' name-value argument.

bafter m:mid inserts a breakpoint after the method with the method ID mid.

bafter blk inserts a breakpoint after each method for the block blk.

bafter blk mth tid:t inserts a breakpoint after the method mth of block blk in the task with task ID t.

bafter mdlName blk mth tid:t inserts a breakpoint after the method mth of block blk that is executed in the task with task ID t in the referenced model with the name mdlName.

bafter sys inserts a breakpoint after each method in the system sys.

bafter sys mth tid:t inserts a breakpoint after the method mth in the system sys with task id t.

bafter mdl inserts a breakpoint after each method of the model mdl.

bafter mdl mth tid:t inserts a breakpoint after the method mth in the task with task ID t of model mdl.

Input Arguments

collapse all

Method after which to insert breakpoint, specified as a method ID.

Block, specified as one of these options:

  • (t)s:b — Block with index b in system with index s and task with task ID t

  • gcb — Current block

Method name, specified as a string or a character vector. For example, this command sets a breakpoint after the Outputs method of the currently selected block.

bafter gcb Outputs

Task ID, specified as a task ID.

Name of referenced model, specified as a string or a character vector.

System, specified as one of these options:

  • s:sysIdx — System specification, where sysIdx is the system index

  • gcs — Current system

Model name, specified as a string or a character vector.

Tips

To determine the current location within the simulation, use the where function.

Version History

Introduced before R2006a