Documentation

This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

bafter

Insert breakpoint after specified method

Syntax

bafter
ba
bafter m:mid

bafter <sysIdx:blkIdx | gcb> [mth] [tid:TID]
bafter <s:sysIdx | gcs> [mth] [tid:TID]
bafter model [mth] [tid:TID]

Arguments

mid

Method ID

sysIdx:blkIdx

Block ID

gcb

Currently selected block

sysIdx

System ID

gcs

Currently selected system

model

Currently selected model

mth

A method name, e.g., Outputs.Major

TID

Task ID

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

Introduced before R2006a

Was this topic helpful?