HP 68000 Series User Manual page 461

Debugger/simulator
Table of Contents

Advertisement

Module Names
The C language does not contain the concept of a module. Within the context
of the debugger, a module is a scoping level which is identical to the scoping
level of a file in C. Module names (which are generated by the compiler), are
derived from source file names by removing the suffix of the source file. For
example, the module name associated with the source file myfile.c would be
myfile. Module names are used to qualify symbol references within the
program symbol tree. When used as such, they are separated from any
following function name by a \.
Note
If files in two directories have the same name, they will have identical module
names. Since the debugger cannot distinguish between the two modules, all
references will resolve to the last loaded module.
Assembly level modules with multiple code sections. If assembly
language modules have more than one code section, the debugger breaks the
module down into sub-modules. For example, if the source file myfile.s had
three code sections, the modules myfile, myfile_2, and myfile_3 would appear
in the program's symbol tree. This module separation only affects the address
ranges of the module, not the scoping, i.e. all symbols scoped under the file
myfile.s would be scoped under module myfile.
Context. Some symbol references are dependent on the current context. See
the examples in the following tables. The current context is based on the PC
and consists of the current root, current module, and current function. To
display the current context, execute the command:
Program Context Display Return
Example
Symbol Display Default \\
Chapter 10: Expressions and Symbols in Debugger Commands
Symbolic Referencing With Explicit Roots
Comment
Display symbols scoped under the non-program
root.
Symbolic Referencing
439

Advertisement

Table of Contents
loading

This manual is also suitable for:

B1466

Table of Contents