HP 68000 Series, User Manual

Page: 460 / 586

Non-program symbol tree.
This tree is composed of non-program symbols.
Only one non-program symbol tree exists. This tree is made up of:
•
debugger symbols (@PC, @SP, etc.)
•
macros
•
user-defined debugger symbols
The root name of this tree is \\.
Program symbol tree. The second type of symbol tree is the program
symbol tree. The debugger allows up to 30 program trees. This tree is made
up of symbols which exist in the target program. Since there may be multiple
program trees within the debugger, the root of a program tree is specified as
@absfile\\, where absfile is the name of the executable file with its suffix
stripped. For example, the root name of the program tree associated with the
executable file a.out.x would be @a_out\\.
Note Any embedded ’.’ characters in a file name are converted to underscores. This
prevents conflicts with the ’.’ structure operator. For example, the module
name of source file myfile.bar.c would be myfile_bar.
There is no method for generating a list of multiple program trees.
If two or more executable files with the same name are loaded, the debugger
appends an underscore and number to one of the files to make the root names
unambiguous. For example, loading two a.out.x files would result in the
creation of two program trees, with root names a_out and a_out_1.
Whenever the PC is pointing to the code space of a program, the root name of
the program’s symbol tree is the current root. A shorthand notation for
specifying the current root is the symbol \. For example, if the debugger is
invoked without loading an executable file, the current root would be \\, which
would be synonymous with \. However, once an executable file (a.out.x) is
loaded with the PC set to an address within the executable’s code space, the
current root becomes @a_out\\, which would be synonymous with \.
The reserved symbol "@root" points to a character string representing the
name of the current root, and the symbol "@file" points to the name of the file
containing the current PC. These may be empty strings ("") if the PC is outside
of any defined symbol database.
Chapter 10: Expressions and Symbols in Debugger Commands
Symbolic Referencing
438