HP 3000 Manuals HP 3000 Manuals
User Errors (UE411 - 670)
UE411 MESSAGE Postfix "--" not supported
CAUSE An attempt was made to use an unsupported --
postfix operator.
ACTION Make sure there is a space between a - and a unary
- operator (for example 2- -5). -=1 can be used to
decrement.
UE412 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.
UE413 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.
UE414 MESSAGE Misformed global name
CAUSE A : or :: must be followed by a variable name
(string).
ACTION Refer to the "Entering Variable Names" section in
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see how to specify global variables.
UE415 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.
UE416 MESSAGE Need a ":" after the number
CAUSE In specifying a variable, proc:depth:var was
entered incompletely (:var was missing).
ACTION Refer to the l (list) command listing in Chapter 4
of the HP Symbolic Debugger/iX User's Guide to see
a list of valid expression for variables.
UE417 MESSAGE Invalid local name
CAUSE In specifying a variable, proc[:depth]:var was
entered incorrectly. The variable var must be a
valid variable name in the specified procedure, at
the specified depth.
UE418 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.
UE419 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.
UE420 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.
UE421 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.
UE422 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
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide.
UE423 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.
UE424 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 Chapter
4 of the HP Symbolic Debugger/iX User's Guide for
more information about search commands.
UE425 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.
UE426 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 Chapter 4 of the HP Symbolic
Debugger/iX User's Guide to see valid data viewing
formats.
UE427 MESSAGE Format is missing "\"
CAUSE Because the command ends with a \, the debugger
expects a format.
ACTION Re-enter the command with a format or without the
ending \.
UE428 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 Table 4-3 in Chapter 4 of the HP Symbolic
Debugger/iX User's Guide to see valid data viewing
formats.
UE429 MESSAGE 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 record or union.
ACTION Use the \t display format for more information.
UE430 MESSAGE This does not appear to be a struct or union
CAUSE The debugger tried and failed to dump the contents
of a data object that was not a struct or union.
ACTION Use the \t display format for more information.
UE431 MESSAGE No count given for b command
CAUSE The debugger expected a breakpoint count after the
\.
ACTION Re-enter the command with a breakpoint count, or
with no \.
UE433 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.
UE434 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.
UE435 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 Chapter 4
of the HP Symbolic Debugger/iX User's Guide for
more information.
UE438 MESSAGE Exiting command line procedure call
CAUSE The command line procedure call environment
terminated for an unusual reason, such as
encountering a breakpoint 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.
UE439 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 attempting 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.
UE440 MESSAGE Argument list too long
CAUSE Arguments to the run command exceeded 1024 bytes.
ACTION Re-enter the run command with fewer arguments.
UE441 MESSAGE Can't goto a location in another procedure
CAUSE The line number given to the g (goto) command was
not an executable source line in the top procedure
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 on the top of the child
process stack.
UE443 MESSAGE Signal actions are "i", "r", "s", "Q"
CAUSE An invalid signal action was given.
ACTION Re-enter the command with a valid action: i
(ignore), r (report), s (stop), or Q (quietly
change signal action).
UE444 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.
UE445 MESSAGE It appears that there's no debugging information
in FILE
CAUSE The program you are trying to debug doesn't contain
debug information.
ACTION Recompile the program with the appropriate
info-string debugging (e.g., info = -g), or debug
the program at the assembly language level.
UE446 MESSAGE Misformed hex number
CAUSE 0x or 0X was given without digits following.
ACTION Re-enter the command with a valid hexadecimal
number.
UE447 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.
UE448 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 an equivalent backslash sequence.
ACTION Re-enter the command enclosing the character
constant in single quotation marks (').
UE449 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.
UE450 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.
UE451 MESSAGE Macros processing overflow
CAUSE While evaluating a user 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.
UE452 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 on the structure object
to examine its type information.
UE453 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 on the array object
to examine its type information.
UE455 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).
UE456 MESSAGE No such field name "NAME" for that record
CAUSE The record did not contain a field of that NAME.
ACTION Use the \t display format for more information.
UE457 MESSAGE No such field name "NAME" for that struct
CAUSE The struct did not contain a field of that NAME.
ACTION Use the \t display format for more information.
UE458 MESSAGE No such field name "NAME" for that union
CAUSE The union did not contain a field of that NAME.
ACTION Use the \t display format for more information.
UE459 MESSAGE Illegal cast
CAUSE The expression contains an illegal cast.
ACTION Re-enter the command with a valid expression. When
casting with a class, structure, or union type, the
keyword class, struct, or union must be given.
UE461 MESSAGE No child process or corefile
CAUSE The debugger attempted an operation that required
an active child process or a core file.
ACTION Start a child process using any of the r (run) or s
(step) commands, or restart the debugger on a valid
core file.
UE464 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.
UE465 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 and
writable by the user.
UE466 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.
UE475 MESSAGE Count must be positive
CAUSE The count argument given to the c (continue)
command is negative or 0.
ACTION Re-enter the command with a positive count (or
none).
UE476 MESSAGE Too many characters in wide-character constant
CAUSE More than one valid (possibly multi-byte) character
was entered.
ACTION Re-enter the expression with one character
constant.
UE477 MESSAGE Wide string constant too long; truncating to NUM
wide-characters
CAUSE Not enough buffer space was available in the user
process to store the entire string constant
(maximum is 127).
ACTION Enter a shorter string constant.
UE479 MESSAGE Empty hex escape sequence
CAUSE An invalid ANSI C hexadecimal escape sequence was
entered.
ACTION Replace the invalid escape sequence with a valid
one of the form \xhh.
UE480 MESSAGE Long double function calls are not supported
CAUSE There was an attempt to call from the command line
a function whose return type is long double.
ACTION This is not supported.
UE481 MESSAGE Long double parameters are not supported in
command line function calls
CAUSE There was an attempt to call from the command line
a function which expects a long double parameter.
ACTION This is not supported.
UE482 MESSAGE Unknown print-mode
CAUSE There was an attempt to assign an illegal value to
the $print debugger variable.
ACTION Assign one of these values: ASCII, native, raw.
UE483 MESSAGE Misformed binary number
CAUSE A misformed binary number was found in an
expression.
ACTION Replace the misformed number with a valid one. (0b
or 0B followed by one or more 0's or 1's)
UE484 MESSAGE Can't open "FILE" as state file
CAUSE The file already exists and is not writable, or the
directory has the wrong permissions.
ACTION Remove the old file, or make the directory writable
and executable.
UE486 MESSAGE Can't open "FILE" as restore file
CAUSE The file doesn't exist or the directory is not
readable.
ACTION Enter a valid file name or add read permission to
the directory.
UE488 MESSAGE No restore name specified
CAUSE No file name was specified with the -R option.
ACTION Invoke the debugger with a restore file name or
don't provide the -R option.
UE490 MESSAGE Wrong objectfile for this statefile
CAUSE The save file specified was not created with the
object file you are trying to debug.
ACTION Specify a valid state file, or if you must use the
one originally specified, start the debugger and
use the file as a playback file. Be sure to read
the warnings related to state files before doing
this.
UE605 MESSAGE Incompatible debug information
CAUSE The debugger was invoked on a file linked on a
older version of the operating system.
ACTION Try relinking your program. If that doesn't solve
the problem, you will have to recompile the
program.
UE626 MESSAGE Attempt to read from ODD address
CAUSE An attempt to read from a non-word or half-world
boundary was made.
ACTION Do not try to read from an odd address. Note:
Memory accesses are done word-at-a-time, regardless
of how data is formatted in memory.
UE632 MESSAGE Wide-character constant not allowed ($lang must
be 'C')
CAUSE Attempt to use a wide character constant while the
language is not C.
ACTION Set $lang to C and re-enter the expression.
UE642 MESSAGE No child process AND no corefile registers
CAUSE The debugger attempted an operation that required
an active child process or a core file.
ACTION Start a child process using any of the r (run) or s
(step) commands, or restart the debugger on a valid
core file.
UE644 MESSAGE - registers bad in core file
CAUSE Unexpected register save area size. The core file
might be corrupted.
ACTION Create a new core file.
UE645 MESSAGE - exec area bad in core file
CAUSE Unexpected exec area size. The core file might be
corrupted.
ACTION Create a new core file.
UE654 MESSAGE Breakpoint count ignored
CAUSE A count is meaningless for class, overload, or
instance breakpoints on multiple member functions.
ACTION None required. The count was ignored but the
breakpoint was set.
UE655 MESSAGE This does not appear to be a struct or union
CAUSE The S display format was specified but the type of
the object to print is not a struct or union.
ACTION If you want to do a formatted dump of an address,
cast the address to some struct or union.
UE659 MESSAGE No functions
CAUSE There are no functions to list starting with the
provided prefix.
ACTION Re-enter the command with a valid function prefix,
or just use the lp (list procedure) command with no
prefix to see a list of all the functions.
UE661 MESSAGE Cannot view (no debug information for file)
CAUSE A location was specified as file:procedure and the
file is not in the debugger's list of files for
which it has debugging information.
ACTION Re-enter the command with a valid file name.
UE662 MESSAGE Cannot set breakpoint (no debug information for
file)
CAUSE The breakpoint location was specified as
file:procedure and the file is not in the
debugger's list of files for which it has debugging
information.
ACTION Re-enter the command with a valid file name. Use
the lf (list files) command to list all valid
source files and the path name you must use.
UE663 MESSAGE Invalid file on "breakpoint" command
CAUSE A file specified as part of a breakpoint location
is not known to the debugger.
ACTION Re-enter the command with a valid file name. Use
the lf (list files) command to list all valid
source files and the path name you must use.
UE664 MESSAGE Invalid procedure on "breakpoint" command
CAUSE A procedure specified as part of a breakpoint
location is not known to the debugger.
ACTION Re-enter the command with a valid procedure name.
Use the lp (list procedures) command to see a list
of all valid procedures.
UE665 MESSAGE Invalid label on "breakpoint" command
CAUSE A label specified as part of a breakpoint location
is not known to the debugger.
ACTION Re-enter the command with a valid label name.
UE666 MESSAGE Invalid class on "breakpoint" command
CAUSE A class specified as part of a breakpoint location
is not known to the debugger.
ACTION Re-enter the command with a valid class name.
UE669 MESSAGE Invalid file on "continue" command
CAUSE A file specified as part of a continue location is
not known to the debugger.
ACTION Re-enter the command with a valid file name. Use
the lf (list files) command to list all valid
source files and the path name you must use.
UE670 MESSAGE Invalid procedure on "continue" command
CAUSE A procedure specified as part of a continue
location is not known to the debugger.
ACTION Re-enter the command with a valid procedure name.
Use the lp (list procedures) command to see a list
of all valid procedures.