This chapter lists messages that you may encounter while using
HP Symbolic Debugger. Self-explanatory messages and those which
relate to syntax errors, such as missing or extraneous characters
in commands, are not listed in this chapter.
To assist you in finding the solution to a problem, several
messages may be displayed. Look up each message in this chapter
to get complete information about the action to take.
Messages are preceded by unique reference numbers that indicate
the error type. Messages, with their message reference numbers,
are listed in this order:
UE300-UE436
User Errors
DB1-DB8
Debugger Errors
Internal error messages, which are in the range of 501 to
579, should not occur with normal debugger use. If
they do occur, report them to your HP support representative.
Child process (program) errors result in signals which are
communicated to the debugger. If a program error occurs while executing
a procedure call from the command line, it is handled like any other
error (in other words, you can investigate the called procedure).
To recover from this, or to abort a procedure call from the command
line, press CNTL-Y.
The following example message has a reference number of UE312 and is
listed below as it appears in this chapter:
UE312 MESSAGE INVALID BREAKPOINT TYPE "TEXT"
A list of abbreviations that are used throughout this chapter
and their meanings follow. Note that in all explanations, commands
are given in long form, but the short form may also be used. Refer
to HP Symbolic Debugger User's Reference Manual for further details.
User errors result from entering incorrect commands or from
using the commands incorrectly. User errors cause the command that
you entered to fail. You must correct the cause of the error and
re-enter the command.
User Errors
UE300
MESSAGE
ATTEMPT TO READ ON NON-WORD BOUNDARY
CAUSE
The debugger cannot read on a non-word aligned address.
ACTION
Do not try to read at a non-word boundary. An incorrect reference
to a data item has probably been made. Note: Memory accesses are done
word-at-a-time, regardless of how data is formatted in memory.
UE301
MESSAGE
ATTEMPT TO WRITE TO ODD ADDRESS
CAUSE
An attempt to write a value on a non-word or half-word boundary
was made.
ACTION
Do not try to write to an odd address. Note: Memory accesses are
done word-at-a-time, regardless of how data is formatted in
memory.
UE302
MESSAGE
ADDRESS NOT FOUND
CAUSE
The address is part of a command and is invalid.
It is probably out of range.
ACTION
Check the validity of the address and re-enter the command.
UE303
MESSAGE
CANNOT READ THAT LOCATION
CAUSE
Access to the child process failed, possibly caused
by an invalid address.
ACTION
Check the validity of the address and re-enter the command.
UE304
MESSAGE
NO CHILD PROCESS
CAUSE
The debugger attempted an operation that required
a child process that does not exist (was not running).
ACTION
To start a child process, use any of the run or
step commands.
UE306
MESSAGE
ATTEMPT TO WRITE TO NON-WORD BOUNDARY.
CAUSE
The debugger cannot write to a non-word aligned address.
ACTION
Do not try to write to a non-word boundary. An incorrect reference
to a data item has probably been made. Note: Memory accesses are done
word-at-a-time, regardless of how data is formatted in memory.
UE307
MESSAGE
CANNOT WRITE THAT LOCATION
CAUSE
Access to a child process failed; this may have
been caused by an invalid address.
ACTION
Check the validity of the address and re-enter the command.
UE308
MESSAGE
BAD ACCESS TO CHILD PROCESS
CAUSE
Failed to read data from or write data to a child process. This may
have been caused by an invalid address (for example, dereferencing an
invalid pointer), or by an attempt to place a breakpoint in an
unwritable child process code space.
ACTION
Check the validity of the data and re-enter the command.
UE309
MESSAGE
CAN'T SET BREAKPOINT (INVALID ADDRESS)
CAUSE
The address of the specified breakpoint command
was invalid or unknown.
ACTION
Re-enter the breakpoint command
with a correct address.
UE310
MESSAGE
STACK ISN'T THAT DEEP
CAUSE
The debugger tried to set a breakpoint or view a procedure at an
invalid depth. The child process stack was not that deep.
ACTION
Use the trace command to list the child process stack.
UE311
MESSAGE
NO SYMBOLS FOR THAT PROCEDURE
CAUSE
The debugger tried to set a breakpoint using a stack depth,
when the procedure at that stack depth was non-debuggable.
ACTION
Try setting a breakpoint-address using the name
of the procedure; for example, ba xxx.
UE312
MESSAGE
INVALID BREAKPOINT TYPE "TEXT"
CAUSE
TEXT was an invalid breakpoint type.
ACTION
Refer to the "Breakpoint Commands" section in the
HP Symbolic Debugger User's Reference Manual to
see valid breakpoint commands.
UE314
MESSAGE
INVALID LINE NUMBER ON "CMD" COMMAND
CAUSE
The quantity given for a line number on a breakpoint,
view, or continue command,
was an invalid numeric expression.
ACTION
Re-enter the command with a valid expression.
UE315
MESSAGE
NO SUCH PROCEDURE OR FILE NAME "TEXT"
CAUSE
An attempt was made to set a breakpoint, or continue to a procedure
or file TEXT that did not exist, or was non-debuggable.
ACTION
Use the lp (list procedures) command to list all
known debuggable procedures and use the lf (list files)
command to list all known source files.
UE316
MESSAGE
PROCEDURE "PROC" NOT FOUND WHERE SPECIFIED
CAUSE
The nesting of procedure PROC was not properly specified.
ACTION
Use the trace command to list the stack.
UE317
MESSAGE
LABEL "TEXT" NOT FOUND WHERE SPECIFIED
CAUSE
The proc #label was entered incorrectly and that label
is not found in the named procedure.
ACTION
Re-enter the command, giving a valid proc #label
combination.
UE318
MESSAGE
NO COUNT GIVEN FOR "CMD" COMMAND
CAUSE
The user failed to specify a breakpoint count (after the \) for a
breakpoint command. Or, an attempt was made to use the
breakpoint count command on an existing breakpoint.
ACTION
Refer to the "Breakpoint Commands" section in the
HP Symbolic Debugger User's Reference Manual to
see the correct syntax for breakpoint commands.
UE319
MESSAGE
COUNT MUST BE POSITIVE OR NEGATIVE
CAUSE
A count of zero was given for a breakpoint or
breakpoint count command.
ACTION
Re-enter the command with a non-zero count.
UE320
MESSAGE
MUST SPECIFY A MACRO NAME
CAUSE
The def command was entered without arguments.
ACTION
Refer to the "Macro Facility Commands" section in
the HP Symbolic Debugger User's Reference Manual to
see the correct syntax for the def command.
UE321
MESSAGE
"NAME" IS NOT A VALID MACRO NAME
CAUSE
The debugger tried to define a macro via the def command
where the NAME specified was not a string of alphanumeric characters
beginning with a letter.
ACTION
Re-enter the def command using a string of characters
beginning with a letter for the macro name.
UE322
MESSAGE
MUST SPECIFY WHICH MACRO TO DELETE
CAUSE
The undef command was entered to delete or undefine a macro
without giving the name of the macro to delete.
ACTION
Use the lm (list macros) command to list all defined
macros.
UE323
MESSAGE
UNKNOWN NAME OR COMMAND "NAME"
CAUSE
An unrecognized string (NAME) was encountered as
a debugger command.
ACTION
Refer to the HP Symbolic Debugger/XL Quick Reference Guide
to see tables of valid debugger commands.
UE324
MESSAGE
UNKNOWN COMMAND "CMD" (NUM)
CAUSE
The command CMD (internal value NUM) is not supported.
The message "Unknown name or command" is usually
displayed.
ACTION
Refer to the HP Symbolic Debugger/XL Quick Reference Guide
to see tables of valid debugger commands.
UE326
MESSAGE
EMPTY ASSERTION NOT ADDED
CAUSE
The assertion command was given without an associated command
list.
ACTION
Re-enter the command and include a command-list within
braces ({ }).
UE328
MESSAGE
NO BREAKPOINT SET AT CURRENT LOCATION
CAUSE
An attempt was made to activate, delete, or suspend
a breakpoint where no breakpoint was defined.
ACTION
Use the lb (list breakpoints) command to see where
breakpoints are set.
UE329
MESSAGE
ADDRESS IS REQUIRED AFTER "CMD"
CAUSE
The ba (breakpoint address) command must be followed
by a code address.
ACTION
Use a valid code address (symbolic or numeric) with
the command.
UE330
MESSAGE
INVALID DEPTH GIVEN FOR "CMD" COMMAND
CAUSE
An attempt was made to specify a depth that is not
a number greater than or equal to 0.
ACTION
Re-enter the appropriate command with a valid depth.
UE331
MESSAGE
DEPTH MUST BE AN INTEGER
CAUSE
An attempt was made to specify a stack depth that
is not a number.
ACTION
Re-enter the command and specify an integer depth.
UE332
MESSAGE
"CMD" NOT ALLOWED WHILE RUNNING ASSERTIONS
CAUSE
These commands cannot be executed while assertions are active:
c (continue), C (Continue),
r (run), R (Run),
s (step), S (Step),
or k (kill).
If one of these commands appears in an assertion command list, it
must follow an x (exit)
command with a non-zero modifier.
ACTION
Exit assertion mode to execute the command or delay using
the command.
UE333
MESSAGE
"da," "db," OR "dp" IS REQUIRED
CAUSE
The d (delete) command has only three valid
variations. This d (delete) command was followed by
something other than an assertion, breakpoint,
or procedure command.
ACTION
Refer to the HP Symbolic Debugger User's Reference Manual
to see valid delete commands.
UE334
MESSAGE
MUST SPECIFY WHICH ASSERTION TO SUSPEND
MUST SPECIFY WHICH ASSERTION TO DELETE
CAUSE
The number of the assertion to suspend or delete
was not specified.
ACTION
Use the la (list assertions) command to find the number
of the assertion to suspend or delete.
UE335
MESSAGE
"Directory" COMMAND NEEDS A DIRECTORY NAME
(IN QUOTES)
CAUSE
The D (Directory) command was invoked without
specifying a directory name surrounded by double quotation
marks ( " ).
ACTION
Re-enter the D (Directory) command and enclose a
valid directory name in quotation marks ( " ).
UE336
MESSAGE
INVALID EXPRESSION FOR DEPTH ON "CMD" COMMAND
CAUSE
The CMD command was given with an expression for a depth
that the debugger cannot evaluate.
ACTION
Use the t (trace) command to view the stack for
the proper procedure and depth.
UE337
MESSAGE
"format" COMMAND NEEDS A STRING ARGUMENT
CAUSE
The f (format) command was followed by something
other than null or a string in quotation marks.
ACTION
Refer to the "Miscellaneous Commands" section in the HP Symbolic
Debugger User's Reference Manual for more information about the
f (format) command.
UE338
MESSAGE
"goto" MUST BE FOLLOWED BY A LINE NUMBER
CAUSE
A g (goto) command was given without a numeric
argument or valid label.
ACTION
Refer to the "Miscellaneous Commands" section in the HP Symbolic
Debugger User's Reference Manual for more information about the
g (goto) command.
UE339
MESSAGE
MISSING "{"
CAUSE
The i (if) command did not have a brace ( { )
following the conditional expression. Or, the expression might have
been entered incorrectly.
ACTION
Re-enter the expression, enclosing the command-lists
in braces.
UE341
MESSAGE
MAP IS NOT SUPPORTED
CAUSE
Your version of the debugger does not support the M
(Map) command, because core files are unsupported.
ACTION
Do not enter the M (Map) command.
UE343
MESSAGE
INVALID EXPRESSION GIVEN FOR "CMD" COMMAND
CAUSE
A non-numeric expression was entered as part of the s
(step), S (Step), t (trace),
T (Trace), and sa (suspend assertion)
commands.
ACTION
Re-enter the command with a correct numeric expression.
UE344
MESSAGE
"t" MUST BE FOLLOWED BY "a", "b", "c", "m", or "r",
OR EXPRESSION
CAUSE
As part of the t (toggle) command, the
t (toggle) was not followed by one of these commands:
a (assertion), b (breakpoint),
c (case), m (macros), or r
(recording).
ACTION
Refer to the individual command listings in the
HP Symbolic Debugger User's Reference Manual to see valid
toggle commands.
UE345
MESSAGE
INVALID WINDOW SIZE
CAUSE
The numeric expression given for the new window size on the window
command was not a valid numeric expression or was outside the range
of 1 to 21.
ACTION
Re-enter the command with a valid numeric expression within
the range of 1 to 21.
UE346
MESSAGE
"exit" IS ONLY ALLOWED WHILE RUNNING ASSERTIONS
CAUSE
The debugger tried to exit the assertions mode while assertions
were not active.
ACTION
Refer to the x (exit) command listing in the
HP Symbolic Debugger User's Reference Manual.
UE348
MESSAGE
NO PLAYBACK NAME SPECIFIED
CAUSE
The < or << command
was given without a file name argument.
ACTION
Re-enter the command with the playback file name.
UE349
MESSAGE
CAN'T OPEN "FILE" AS PLAYBACK FILE
CAUSE
The system failed to open the specified playback file.
ACTION
Check the file path and permissions.
UE350
MESSAGE
CAN'T OPEN "FILE" AS RECORD FILE
CAUSE
The system failed to open the specified record file.
ACTION
Check the file path and permissions.
UE351
MESSAGE
OPERATOR STACK OVERFLOW
CAUSE
The expression was too complicated for the expression handler
to parse. A combination of more than 15 nested parentheses and/or
pending operators may be the cause.
ACTION
Re-enter the expression, using less than 15 nested
parentheses.
UE352
MESSAGE
OPERATOR STACK UNDERFLOW
CAUSE
The expression handler failed. This may have been
caused by a corrupt environment or a parsing problem.
ACTION
Re-enter the expression in an alternate form, if possible.
UE353
MESSAGE
DATA TOO BIG TO PUT IN THE CHILD PROCESS
CAUSE
A string constant or other data was larger than the total size of
the buffer in xdbend.lib.sys
ACTION
Re-enter a smaller string constant or data item,
if applicable.
UE354
MESSAGE
CAN'T STORE INTO A CONSTANT
CAUSE
The left side of an assignment statement was found
to be a constant; it cannot be modified.
ACTION
Use the \t display format for information on the assigned
variable.
UE355
MESSAGE
CAN'T SET ANY REGISTERS
CAUSE
Setting registers incorrectly is inherently dangerous
and can lead to complete lockup of the operating system.
ACTION
Only use the g (goto) command to make limited, safe
changes to the program counter ($pc). Avoid changing register values
directly.
UE356
MESSAGE
STRING TOO LONG FOR ASSIGNMENT
CAUSE
An attempt was made to assign a string over 1024
bytes to an HP FORTRAN 77 CHAR*, HP Pascal string, or HP Pascal
packed array of char.
ACTION
Use the \t display format for type information of the string
assigning to, and re-enter the command with an appropriately sized
string.
UE357
MESSAGE
INCOMPATIBLE OPERANDS FOR STRING ASSIGNMENT
CAUSE
An attempt was made to assign to an HP FORTRAN 77 CHAR*,
HP Pascal string, or HP Pascal packed array of char, something other
than an HP FORTRAN 77 CHAR*, HP Pascal string, HP Pascal packed
array of char, a string constant, or a character constant.
ACTION
Re-enter the command with a proper assignment.
UE358
MESSAGE
CAN'T DEREFERENCE A CONSTANT
CAUSE
An attempt was made to dereference a constant.
ACTION
Use the \t format to find the type of the object to be
displayed.
UE359
MESSAGE
CAN'T TAKE THE ADDRESS OF A CONSTANT
CAN'T TAKE THE ADDRESS OF A REGISTER
CAUSE
Operand of &, $addr, or addr operator is
marked as a constant or register type.
ACTION
Use the \t display format to find the type of the object
being displayed.
UE360
MESSAGE
POSTFIX "++" NOT SUPPORTED
POSTFIX "--" NOT SUPPORTED
PREFIX "++" NOT SUPPORTED
PREFIX "--" NOT SUPPORTED
CAUSE
An attempt was made to use an unsupported operator. For example,
++n, --n, n++, n--.
ACTION
Make sure a space is used between a + or -
operator and a unary sign (for example 2- -5). +=1
or -=1 can be used to increment or decrement,
respectively.
UE361
MESSAGE
INVALID COMBINATION OF OPERATOR AND OPERANDS
CAUSE
The debugger tried to perform a numeric operation
on one or more non-numeric operands.
ACTION
Re-enter the command with a valid expression.
UE362
MESSAGE
UNKNOWN OPERATOR (NUM)
CAUSE
An unsupported operator, with internal value NUM,
was pushed on the operator stack.
ACTION
Re-enter the command using an operator known to the current language
or reset $lang to the language in which the operator
is valid.
UE363
MESSAGE
MISFORMED EXPRESSION
CAUSE
An expression was entered incorrectly. The debugger attempts
to show you where the error was detected in the command line. The
error token might be one token beyond the actual error.
ACTION
Re-enter the expression using operators and operands known
to the current language or reset $lang to the language
in which the operator or operand is valid.
UE364
MESSAGE
TWO OPERATORS IN A ROW
CAUSE
The expression handler detected an improper construct
in an expression.
ACTION
Re-enter the command with a valid expression.
UE365
MESSAGE
FORTRAN VARIABLE NOT PURE ARRAY
CAUSE
An attempt was made to dereference an array that had pointer or
function qualifiers, while the current language was set to FORTRAN,
which does not support them.
ACTION
Try again with $lang set to a different language.
UE366
MESSAGE
INVALID REAL NUMBER
CAUSE
The specified numeric expression was not a real number.
ACTION
See the appropriate language reference manual, or Table 4-3 in
this manual, for the format of real numbers.
UE367
MESSAGE
MISFORMED GLOBAL NAME
CAUSE
Colon ( : ) must be followed by a variable name (string).
ACTION
Refer to the "Entering Variable Names" section in the HP Symbolic
Debugger User's Reference Manual to see how to specify global
variables.
UE368
MESSAGE
UNKNOWN GLOBAL
CAUSE
The variable specified with :var was
not a recognized global variable name.
ACTION
Use the lg (list globals) command to list all
known global variables.
UE369
MESSAGE
NEED A ":" AFTER THE NUMBER
CAUSE
Proc:depth:var was entered
incompletely (:var was missing).
ACTION
Refer to the l (list) command listing in the HP
Symbolic Debugger User's Reference Manual to see a list
of variables.
UE370
MESSAGE
INVALID LOCAL NAME
CAUSE
Proc[:depth]:var was entered incorrectly. Var must
be a valid variable name in the specified procedure, at the specified
depth.
UE371
MESSAGE
UNKNOWN LOCAL
CAUSE
The variable specified with proc[:depth]:var was
not a recognized local variable of proc.
ACTION
Use the l (list) command to list all known local
variables of the current proc, or use the T(Trace) command to list the locals, variables, and procedures
on the stack.
UE372
MESSAGE
PROCEDURE "PROC" NOT FOUND AT STACK DEPTH NUM
CAUSE
In proc:depth, the procedure PROC was not on the child
process stack at depth NUM. Either the stack was not that deep,
or the procedure at that depth was not PROC.
ACTION
Use the t (trace) command to list the stack.
UE373
MESSAGE
UNKNOWN LANGUAGE
CAUSE
An attempt was made to modify the current language by assigning an
invalid language designator to the special variable $lang. The
valid language designators are COBOL, Pascal,
FORTRAN, C, and default.
ACTION
Re-enter the command with COBOL, Pascal,
FORTRAN, C, or default as the designator.
UE374
MESSAGE
LOCAL IS NOT ACTIVE
CAUSE
A local variable name was recognized but the procedure it belongs
to was not currently active on the child process stack.
ACTION
Re-enter the command after its procedure has been called.
UE375
MESSAGE
TWO OPERANDS IN A ROW
CAUSE
The expression handler detected an improper construct
in an expression.
ACTION
Refer to the "Entering Expressions" section in the HP Symbolic
Debugger User's Reference Manual (31508-90003).
UE376
MESSAGE
NO SOURCE FILE FOR CURRENT ADDRESS
CAUSE
The given child process address did not map to a
known, debuggable source file.
ACTION
Use the lf (list files) command to view the files the
debugger recognizes, and re-enter the command with an appropriate
address expression.
UE377
MESSAGE
NO SEARCH PATTERN
CAUSE
The search command (/, ?, n (next),
or N (Next)) was given without a search pattern (in
the case of n (next) and N (Next), the previous
search command / or ? was provided without a pattern).
ACTION
Refer to the individual command listings in the
HP Symbolic Debugger User's Reference Manual for
more information about search commands.
UE378
MESSAGE
NO MATCH FOR "TEXT"
CAUSE
The search pattern (TEXT) for the /, ?, n,
(next) or N (Next) command was not found in the
current viewing file. Note that the pattern is a literal, not a
regular expression.
ACTION
Try another pattern or view another file and search
for the pattern.
UE379
MESSAGE
INVALID DISPLAY FORMAT "TEXT"
CAUSE
Given the data display format, or a portion of it,
the TEXT contained invalid syntax.
ACTION
Refer to Table 4-3 in the HP Symbolic Debugger User's Reference
Manual to see valid data viewing formats.
UE381
MESSAGE
LENGTH NOT ALLOWED WITH "TEXT" FORMAT
CAUSE
Given the data display format, the TEXT did not allow the data
length specification because it is irrelevant or implicit in the
format.
ACTION
Refer to the HP Symbolic Debugger User's Reference Manual
to see valid data viewing formats.
UE382
MESSAGE
THIS DOES NOT APPEAR TO BE A STRUCT OR UNION
THIS DOES NOT APPEAR TO BE A RECORD OR UNION
CAUSE
The debugger tried and failed to dump the contents of a data
object that was not a struct, union, or record.
ACTION
Use the \t display format for more information.
UE385
MESSAGE
NO CURRENT PROCEDURE
CAUSE
The debugger tried to list locals for the current
viewing procedure when the procedure was undefined.
ACTION
Use the lp (list procedures) command to list all
the debuggable procedures.
UE386
MESSAGE
NO SUCH PROCEDURE "PROC"
CAUSE
An attempt to list locals of a non-existent, or non-debuggable
procedure PROC was made.
ACTION
Use the lp (list procedures) command to list all
known debuggable procedures.
UE387
MESSAGE
UNRECOGNIZED "l" COMMAND
CAUSE
The l (list) command was given with a second part
that was neither a known procedure name, nor a valid option.
ACTION
Refer to the l (list) command listing in the
HP Symbolic Debugger User's Reference Manual
for more information.
UE388
MESSAGE
":" MUST BE FOLLOWED BY A DEPTH
CAUSE
Proc:depth was entered incorrectly.
ACTION
Refer to the individual command listings in the HP Symbolic
Debugger User's Reference Manual for more information.
UE390
MESSAGE
EXITING COMMAND LINE PROCEDURE CALL
CAUSE
The command line procedure call environment terminated for an
unusual reason, such as a break was encountered during program
execution, or an error was reached before the procedure was
called.
ACTION
Check the procedure call for errors and re-enter
the command line procedure call.
UE391
MESSAGE
CAN'T PASS MORE THAN NUM ARGUMENTS TO CALLED
PROCEDURE
CAUSE
A large limit (NUM) exists on how many parameters can be passed
to a procedure called from the command line.
ACTION
Check the number of parameters for the procedure you are attemping
to call. If the limit (NUM) is less than the number of parameters in
the procedure, that procedure cannot be called from the
command line.
UE392
MESSAGE
ARGUMENT LIST TOO LONG
CAUSE
Arguments to the run command exceeded 1024 bytes.
ACTION
Re-enter the run command with fewer arguments.
UE393
MESSAGE
CAN'T GOTO A LINE OUTSIDE OF THE CURRENT PROCEDURE
CAUSE
The line number given to the g (goto) command was not
an executable source line in the top procedure or paragraph on the
child process stack. This is not always the same as the current
viewing procedure.
ACTION
Re-enter the g (goto) command with a line number
within the procedure or paragraph on the top of the child
process stack.
UE396
MESSAGE
UNKNOWN NAME
CAUSE
An unrecognized string (procedure or variable name)
was encountered in an expression.
ACTION
Use the lp (list procedures), lg (list
globals), l (list), lc (list commons),
or ll (list labels) command to list all known procedures,
globals, locals, commons, or labels.
UE398
MESSAGE
MISFORMED HEX NUMBER
CAUSE
0x or 0X was given without digits following.
ACTION
Re-enter the command with a valid hexadecimal number.
UE399
MESSAGE
MISFORMED OCTAL NUMBER
CAUSE
An octal number starting with 0 contains an 8 or 9.
ACTION
Re-enter the command with the correct octal number.
UE400
MESSAGE
CHARACTER CONSTANT IS MISSING ENDING
CAUSE
Token parsed as a character constant is missing a trailing single
quotation mark ('). This applies to a single quotation mark followed
by a single character or equivalent, backslash sequence.
ACTION
Re-enter the command enclosing the character constant
in single quotation marks (').
UE401
MESSAGE
STRING CONSTANT IS MISSING ENDING "
CAUSE
Token parsed as a string constant was missing a trailing double
quotation mark before the end of the command line.
ACTION
Re-enter the string with a beginning and ending
double quotation marks.
UE402
MESSAGE
MACROS NESTED TOO DEEPLY
CAUSE
A user specified macro has caused the evaluation of over 20 macro
definitions during its evaluation. The debugger cannot evaluate macros
nested this deep. This error can also be caused by a recursive macro
definition.
ACTION
Redefine the macro using fewer than 20 macro definitions, or
remove the recursive definition.
UE403
MESSAGE
MACROS PROCESSING OVERFLOW
CAUSE
While evaluating a userh specified macro, the buffer used to hold
the resulting definition for this macro was about to overflow,
and the processing for this macro terminated unsuccessfully.
ACTION
Undefine the unnecessary macros and redefine the macro.
UE404
MESSAGE
SORRY, YOU CAN'T ACCESS A NAKED FIELD
CAUSE
An attempt was made to refer to a field by name without specifying
the qualifying structure (for example, union, record,
pointer, etc.).
ACTION
Use the \t display format for more information.
UE405
MESSAGE
TOO MANY SUBSCRIPTS
CAUSE
An attempt was made to dereference an array with more dimensions
than it was declared to have. However, HP C does allow you to
dereference pointers in this manner.
ACTION
Use the \t display format for more information.
UE407
MESSAGE
INVALID FIELD ACCESS: "NAME"
CAUSE
An attempt was made to do a field dereference of
an object (NAME) that was not a structure or union.
ACTION
Use the \t display format to determine the characteristics
of the object (NAME).
UE408
MESSAGE
NO SUCH FIELD NAME "NAME" FOR THAT RECORD
NO SUCH FIELD NAME "NAME" FOR THAT STRUCT
NO SUCH FIELD NAME "NAME" FOR THAT UNION
CAUSE
Struct (union, record) did not contain a field of that NAME.
ACTION
Use the \t display format for more information.
UE411
MESSAGE
OPERAND STACK OVERFLOW
CAUSE
An expression was too complicated for the expression handler to
parse. A combination of more than 15 nested parentheses and/or
pending operators may be the cause.
ACTION
Re-enter the expression, using less than 15 nested
parentheses.
UE412
MESSAGE
CAN'T EXECUTE CHILD PROGRAM
CAUSE
The debugger could not execute the object file given.
ACTION
Check to see that the file is executable.
UE413
MESSAGE
WINDOW MODE REQUIRED FOR THIS COMMAND
CAUSE
The debugger was probably invoked with the -L option.
ACTION
Verify that you are using an HP terminal and rerun
the debugger without the -L option.
UE415
MESSAGE
NO SUCH FIELD: "NAME"
CAUSE
The simple field NAME or field list specified does
not exist.
ACTION
Check the declaration for the correct field name
or field list.
UE416
MESSAGE
NON-UNIQUE FIELD LIST
CAUSE
The field name or field list specified does not
uniquely identify a single field.
ACTION
Use a more complex field list to ensure it identifies
a single field.
UE418
MESSAGE
CAN'T MIX . AND OF OPERATORS
CAUSE
The field list includes both the . and
of operators.
ACTION
Use only the . or of operator.
UE419
MESSAGE
ONE ARRAY SUBSCRIPT EXPECTED
CAUSE
The field specified is a table or one of the field's
ancestors is a table, but no array subscript was given.
ACTION
Determine which field is a table, and use the appropriate
subscript.
UE420
MESSAGE
LIST OF <NUMBER> ARRAY SUBSCRIPTS EXPECTED
CAUSE
The field specified is a table and/or one or more of the field's
ancestors is a table; <number> subscripts
are required, but no array subscripts were given.
ACTION
Determine which fields are tables, and use the appropriate <
number> of subscripts.
UE421
MESSAGE
NOT ENOUGH ARRAY SUBSCRIPTS, EXPECTED
<NUMBER>
CAUSE
There are more tables among the field and its ancestors than
there were subscripts given.
ACTION
Determine which fields are tables, and supply <
number> subscripts.
UE422
MESSAGE
UNEXPECTED ARRAY SUBSCRIPT LIST
CAUSE
Neither the field specified nor any of its ancestors
are tables, but one or more subscripts was given.
ACTION
Do not give a list of subscripts.
UE423
MESSAGE
CAN'T MOVE TO A CONSTANT
CAUSE
The item which is the destination of the move is a constant.
ACTION
Do not attempt to store into a constant, or look
at the declarations to determine the correct field name.
UE424
MESSAGE
CAN'T MOVE TO THAT DESTINATION
CAUSE
The item which is the destination of the move is
of a type into which the debugger can not store.
ACTION
Do not attempt to store into that item, or look at the declarations
to determine the correct field name.
UE425
MESSAGE
CAN'T HANDLE EDITED FIELDS AS DESTINATION
CAUSE
The item which is the destination of the move is
an edited field.
ACTION
None, the debugger can not currently handle edited fields as the
source or destination of a mov (move) command.
UE426
MESSAGE
CAN'T HANDLE EDITED FIELDS AS SOURCE
CAUSE
The item which is the source of the move is an edited field.
ACTION
None, the debugger can not currently handle edited fields as the
source or destination of a mov (move) command.
UE427
MESSAGE
CAN'T MOVE NUMERIC FIELD TO ALPHABETIC FIELD
CAUSE
The source of the move is a numeric field, while
the destination field is alphabetic.
ACTION
None, moving a numeric field to an alphabetic field
is illegal.
UE428
MESSAGE
CAN'T MOVE NUMERIC FIELD WITH A FRACTION TO ALPHANUMERIC
FIELD
CAUSE
The source of the move is a numeric field which has a fraction,
while the destination field is alphanumeric.
ACTION
None, moving a numeric field with a fraction to
an alphanumeric field is illegal.
UE429
MESSAGE
CAN'T MOVE ALPHABETIC FIELD TO NUMERIC FIELD
CAUSE
The source of the move is an alphabetic field, while
the destination field is numeric.
ACTION
None, moving an alphabetic field to a numeric field
is illegal.
UE430
MESSAGE
CAN'T MOVE ALPHANUMERIC FIELD CONTAINING NON-DIGIT TO NUMERIC
FIELD
CAUSE
The source of the move is an alphanumeric field containing
a non-digit, while the destination is numeric.
ACTION
None, moving an alphanumeric field containing a non-digit
to a numeric field is illegal.
UE431
MESSAGE
INVALID SIGN IN PACKED DECIMAL NUMBER
CAUSE
The packed decimal field that is either being displayed or being
used as the source of a move contains an invalid sign field.
ACTION
Use either a data field that redefines the packed decimal field,
or use the group field that contains the packed decimal
data field.
UE432
MESSAGE
INVALID DIGIT IN PACKED DECIMAL NUMBER
CAUSE
The packed decimal field that is either being displayed or being
used as the source of a move contains an invalid digit.
ACTION
Use either a data field that redefines the packed decimal field,
or use the group field that contains the packed decimal
data field.
UE433
MESSAGE
INVALID SIGN OVERPUNCH IN DISPLAY NUMBER
CAUSE
The display field that is either being displayed or being used as
the source of a move contains an invalid sign overpunch.
ACTION
Use either a data field that redefines the display field, or use
the group field that contains the display field.
UE434
MESSAGE
INVALID SEPARATE SIGN IN DISPLAY NUMBER
CAUSE
The display field that is either being displayed or being used as
the source of a move contains an invalid separate sign.
ACTION
Use either a data field that redefines the display field, or use
the group field that contains the display data field.
UE435
MESSAGE
TOO MANY ARRAY SUBSCRIPTS, EXPECTED <NUMBER>
CAUSE
There are less tables among the field and its ancestors than
there were subscripts.
ACTION
Determine which fields are tables, and supply <
number> subscripts.
UE436
MESSAGE
SUBSCRIPT NUMBER <SUBSCRIPT> OUTSIDE RANGE <LOW>
TO <HIGH>.
CAUSE
Subscript number <subscript> was outside the valid
range of <low> to < high>.
Assigning to NUM byte object from NUM byte object; moved NUM
bytes
CAUSE
The object on the left side of an assignment was not equal to the
size of the right side of the expression. The debugger copied
a series of bytes equal in size to the left side of the assignment
statement.
ACTION
Re-enter the command, using expressions of equal
length, or else results based on truncation will occur.
DB2
MESSAGE
WARNING: "FILE" DOES NOT APPEAR TO HAVE LINE
SYMBOLS
CAUSE
When opening the source file (FILE) associated with
a procedure, no entries in the source line table were found for
the procedure. The procedure may not have any executable lines,
or the object file may have been corrupted.
ACTION
Recompile the program with the symbolic debugger option.
DB3
MESSAGE
WARNING: "FILE1" IS YOUNGER THAN "FILE2"
CAUSE
The source file (FILE1) modification time is newer
than the object file (FILE2) modification time, so the source file may
not correspond to the code in object file.
ACTION
Recompile the source file with the symbolic debugger option
to update the object file.
DB7
MESSAGE
WARNING: CODE IS SHARED; YOU CAN'T SET BREAKPOINTS SO YOU
CAN'T RUN.
CAUSE
The object file was set to a shared mode that prevented
the debugger from writing breakpoints into a child process code
in memory. Because an initial breakpoint is required when starting
a child process, you cannot do any useful debugging without one.
If you try to start a child process, you may receive the message:
"Bad access."
ACTION
If possible, modify the object file to no longer
be in shared mode.
DB8
MESSAGE
WARNING: "XDBEND" WAS NOT LINKED WITH THIS PROGRAM
CAUSE
The special procedure "_end_" was not found in the
symbol table during initialization. If xdbend is
missing, string constants and some other values cannot be stored
in the child process address space when required, resulting in an error
at that time.
ACTION
Re-link the program with xdbend.lib.sys.
DB10
MESSAGE
WARNING: TOO FEW PARAMETERS
CAUSE
An attempt was made to call a debuggable procedure
from the command line with a different number of parameters than
specified in the symbol table. The procedure can still be called,
but it may lead to odd results which depend on the language and
the called procedure.
ACTION
Use the V (View) command to view the procedure to
determine the correct number of parameters.
DB11
MESSAGE
WARNING: TOO MANY PARAMETERS
CAUSE
An attempt was made to call a debuggable procedure
from the command line with a different number of parameters than
specified in the symbol table. The procedure can still be called,
but it may lead to odd results which depend on the language and
the called procedure.
ACTION
Use the V (View) command to view the procedure to
determine the correct number of parameters.