The parameters are as follows:
<FILENAME>
This is an UNIX path specifying a source file. If no file is specified, and the
identifier referenced is not a global symbol in the executable file that was loaded,
then the default file is assumed (the last absolute file specified by a display
local_symbols_in command). A default file is only assumed when other parameters
(such as line) in the --SYMB-- specification expect a file.
line
This specifies that the following numeric value references a line number in the
specified source file.
<LINE#>
Prompts you for the line number of the source file.
<IDENTIFIER>
Identifier is the name of an identifier as declared in the source file.
SCOPE
Scope is the name of the portion of the program where the specified identifier is
defined or active (such as a procedure block).
segment
This indicates that the following string specifies a standard segment (such as
PROG, DATA, or COMN) or a user-defined segment in the source file.
<SEG_NAME>
Prompts you for entry of the segment name.
(<TYPE>)
When two identifier names are identical and have the same scope, you can
distinguish between them by entering the type (in parentheses). Do not type a space
between the identifier name and the type specification. The type will be one of the
following:
filename
Specifies that the identifier is a source file.
module
These refer to module symbols. For Ada, they are packages. Other language
systems may allow user-defined module names.
procedure
Any procedure or function symbol. For languages that allow a change of scope
without explicit naming, SRU assigns an identifier and tags it with type procedure.
static
Static symbols, which includes global variables. The logical address of these
symbols will not change.
task
Task symbols, which are specifically defined by the processor and language system
in use.
:
A colon is used to specify the UNIX file path from the line, segment, or symbol
specifier. When following the file name with a line or segment selection, there
must be a space after the colon. For a symbol, there must not be a space after the
colon.
Chapter 11: Emulator/Analyzer Interface Commands
--SYMB--
387
Summary of Contents for 64780A
Page 1: ...Graphical User Interface User s Guide MC68360 68EN360 Emulator Analyzer HP 64780A ...
Page 20: ...xx ...
Page 21: ...Part 1 Quick Start Guide 1 ...
Page 23: ...1 Getting Started 3 ...
Page 45: ...Part 2 Using The Emulator 25 ...
Page 47: ...2 Plugging into a Target System 27 ...
Page 55: ...Chapter 2 Plugging into a Target System Plugging into the Motorola QUADS Target System 35 ...
Page 59: ...3 Starting and Exiting HP 64700 Interfaces 39 ...
Page 69: ...4 Entering Commands 49 ...
Page 103: ...5 Configuring the Emulator 83 ...
Page 122: ...102 ...
Page 123: ...6 Using the Emulator 103 ...
Page 193: ...7 Using the Emulation Bus Analyzer How to record program execution in real time 173 ...
Page 249: ...8 Making Software Performance Measurements 229 ...
Page 279: ...9 Making Coordinated Measurements 259 ...
Page 295: ...Part 3 Reference 275 ...
Page 297: ...10 Setting X Resources 277 ...
Page 312: ...292 ...
Page 313: ...11 Emulator Analyzer Interface Commands 293 ...
Page 391: ...set Chapter 11 Emulator Analyzer Interface Commands set 371 ...
Page 405: ... SYMB Chapter 11 Emulator Analyzer Interface Commands SYMB 385 ...
Page 422: ...402 ...
Page 460: ...440 ...
Page 461: ...Part 4 Concept Guide 441 ...
Page 463: ...13 Concepts of the EMSIM and EMRAM 443 ...
Page 471: ...Part 5 Installation and Service Guide 451 ...
Page 473: ...14 Installation 453 ...
Page 491: ...Chapter 14 Installation Verifying the Installation 471 ...
Page 493: ...15 Installing Updating Emulator Firmware 473 ...
Page 500: ...480 ...
Page 516: ...496 ...
Page 540: ...520 ...