Debugger : Debugger Commands : LIST Command

LIST Command

The LIST command instructs the Debugger to output a list of objects belonging to the prototyped specification. You can choose whether to list all the objects in the specification, or to select only those of a certain class, subclass or name. The listing does not show the values or status of the objects in the current prototype execution. It merely lists those objects that are within the prototyping scope.

The LIST command can be used in each of four basic forms:

Pdb > LIST
Pdb > LIST object_class
Pdb > LIST object_class subclass
Pdb > LIST object_class list_of_objects
 

For example, the following are valid LIST commands:

Pdb > LIST EVENT EXTERNAL
Pdb > LIST DATA input_value, y*
Pdb > LIST ACTIVITY

 

The order in which the information is displayed is hierarchical for activities and states and alphabetical for events, conditions and data-items. Remember that the command shows all objects in the system, regardless of their current status in the execution.

For example, the command: Pdb > LIST ACTIVITY PRIMITIVE lists the names of all primitive activities in the specification, regardless of which ones are currently active.

Similarly, if you type:

Pdb > LIST STATE NON_BASIC

 

 

the Debugger lists all the non-basic states in all the controlling statecharts in the prototype scope—not only those states which belong to the current configuration.

When applied to non-graphical objects (events, conditions, data-items), the LIST command displays the requested information and, in addition, marks all compound objects as in the following example:

Pdb > LIST EVENT S*
(c) chart1: signal
chart2: switch
(c) chart2: scroll

 

The compoundness attribute allows you to easily identify those elements to which command SET OBJECT cannot be applied.