Debugger : Resolving Name Ambiguity : Keywords

Keywords

There are no reserved words in the Debugger. It is clear from the context whether a word is used as an object name or a Debugger keyword. For example:

Pdb > SET BREAK br_label go

Here, “go” is obviously the name of an event and not a command keyword.

However, in some of the Debugger commands there are cases where both a Debugger keyword and an object name may be given. This occurs in all the SHOW, LIST and TRACE commands - where you can give either an object name or a keyword that denotes a subclass of Rational Statemate objects (for example, “basic,” primitive, etc.) as an argument.

If an object exists whose name is the same as a keyword, and the user wishes to specify this object in a command, its name must be specified within quotes. For example:

Pdb > SET TRACE ACTIVITY PRIMITIVE

 

 

means trace all the primitive activities, while

Pdb > SET TRACE ACTIVITY “PRIMITIVE”

 

 

means trace all the activities whose name is PRIMITIVE.

Generally, each of the keywords used in Debugger commands may be abbreviated. If the abbreviation is ambiguous, then an error message is displayed followed by the list of possible meaning for abbreviation. For example:

Pdb > L

causes the following response:

Ambiguous keyword abbreviation: L. Possible meanings:
LIST
LOAD