HP 3000 Manuals HP 3000 Manuals
User Errors (UE300 - UE410)
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.
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 r (run) or
s (step) commands.
UE305 MESSAGE No child process AND no corefile
CAUSE The debugger attempted an operation that required a
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.
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. Other
possible causes:
* The executable file is already being
debugged in a different debugging session.
* The process you were debugging exec'ed a
different process.
ACTION Check the validity of the data and re-enter the
command. You can also:
* Kill the other debugging session.
* If you need to debug the new process, adopt
it with the -P option.
UE310 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 or location.
UE311 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. This will show you how deep the stack is
and what procedure is at each depth on the stack.
UE312 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 ba (breakpoint address) using the
name of the procedure; for example, ba xxx.
UE313 MESSAGE Invalid breakpoint type "TEXT"
CAUSE TEXT was an invalid breakpoint type.
ACTION Refer to the "Breakpoint Commands" section in
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see valid breakpoint commands.
UE314 MESSAGE Invalid command list, must be enclosed in {}
CAUSE The command list associated with a breakpoint or an
assertion must be enclosed in {}.
ACTION Re-enter the breakpoint or assertion with the
correct syntax.
UE315 MESSAGE Invalid line number on "breakpoint" command
CAUSE The quantity given for a line number on a
breakpoint command was an invalid numeric
expression.
ACTION Re-enter the command with a valid expression.
UE319 MESSAGE Invalid line number on "CMD" command
CAUSE The quantity given for a line number on a b
(breakpoint), v (view), or c (continue) command,
was an invalid numeric expression.
ACTION Re-enter the command with a valid expression.
UE321 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 and find
where PROC is located.
UE323 MESSAGE No count given for "breakpoint 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 bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE324 MESSAGE No count given for "breakpoint" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE325 MESSAGE No count given for "breakpoint address" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE326 MESSAGE No count given for "breakpoint beginning" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE327 MESSAGE No count given for "breakpoint count" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE328 MESSAGE No count given for "breakpoint trace" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE329 MESSAGE No count given for "breakpoint uplevel" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE330 MESSAGE No count given for "breakpoint exit" command
CAUSE The user failed to specify a breakpoint count
(after the \) for a breakpoint command. Or, an
attempt was made to use the bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE331 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 bc (breakpoint count)
command on an existing breakpoint.
ACTION Refer to the "Breakpoint Commands" section in the
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for breakpoint
commands.
UE332 MESSAGE Count must be positive or negative
CAUSE A count of zero was given for a b (breakpoint) or
bc (breakpoint count) command.
ACTION Re-enter the command with a non-zero count.
UE333 MESSAGE Must specify a macro name
CAUSE The def command was entered without arguments.
ACTION Refer to the "Macro Facility Commands" section in
Chapter 4 of the HP Symbolic Debugger/iX User's
Guide to see the correct syntax for the def
command.
UE335 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.
UE336 MESSAGE Unknown name or command "NAME"
CAUSE An unrecognized string (NAME) was encountered as a
debugger command.
ACTION Refer to the HP Symbolic Debugger/iX Quick
Reference to see tables of valid debugger commands.
UE337 MESSAGE Unknown command "CMD"
CAUSE An unrecognized string (CMD) was encountered as a
debugger command.
ACTION Refer to the HP Symbolic Debugger/iX Quick
Reference to see tables of valid debugger commands.
UE339 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 ({ }).
UE341 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.
UE342 MESSAGE Address is required after "breakpoint address"
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.
UE343 MESSAGE Address is required after "CMD"
CAUSE The breakpoint command must be followed by a code
address.
ACTION Use a valid code address (symbolic or numeric) with
the command.
UE344 MESSAGE Invalid depth given for "breakpoint 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.
UE345 MESSAGE Invalid depth given for "breakpoint beginning"
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.
UE346 MESSAGE Invalid depth given for "breakpoint trace"
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.
UE347 MESSAGE Invalid depth given for "breakpoint uplevel"
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.
UE348 MESSAGE Invalid depth given for "breakpoint exit" 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.
UE349 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.
UE350 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.
UE355 MESSAGE Must specify which assertion to delete
CAUSE The number of the assertion to delete was not
specified.
ACTION Use the la (list assertions) command to find the
number of the assertion to delete.
UE358 MESSAGE Invalid expression for depth on "View" command
CAUSE The View 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.
UE359 MESSAGE Invalid expression for depth on "V" command
CAUSE The V 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.
UE364 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.
UE368 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.
UE369 MESSAGE Unknown name "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.
UE372 MESSAGE Must specify which assertion to suspend
CAUSE The number of the assertion to suspend was not
specified.
ACTION Use the la (list assertions) command to find the
number of the assertion to suspend.
UE373 MESSAGE Invalid expression given for "suspend assertion"
command
CAUSE The sa (suspend assertion) command was given with
an expression that the debugger cannot evaluate.
ACTION Use an expression which evaluates to a number.
UE374 MESSAGE Invalid expression given for "sa" command
CAUSE The sa (suspend assertion) command was given with
an expression that the debugger cannot evaluate.
ACTION Use an expression which evaluates to a number.
UE375 MESSAGE Bad magic number NUM
CAUSE The file you are trying to debug is not a valid
executable file.
ACTION Specify a valid executable file for the program to
be debugged.
UE378 MESSAGE Invalid expression given for "step" command
CAUSE A non-numeric expression was entered as part of the
s (step) command.
ACTION Re-enter the command with a correct numeric
expression.
UE379 MESSAGE Invalid expression given for "Step" command
CAUSE A non-numeric expression was entered as part of the
S (Step) command.
ACTION Re-enter the command with a correct numeric
expression.
UE380 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), or sa
(suspend assertion) command.
ACTION Re-enter the command with a correct numeric
expression.
UE382 MESSAGE Invalid expression given for "trace" command
CAUSE A non-numeric expression was entered as part of the
t (trace) command.
ACTION Re-enter the command with a correct numeric
expression.
UE383 MESSAGE Invalid expression given for "Trace" command
CAUSE A non-numeric expression was entered as part of the
T (Trace) command.
ACTION Re-enter the command with a correct numeric
expression.
UE384 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 a range that is
acceptable for you screen size.
ACTION Re-enter the command with a valid numeric
expression within the range of 1 to the number of
lines on your screen minus 3.
UE387 MESSAGE Invalid expression for mode on "exit" command
CAUSE The x (exit) command was given with an expression
for mode that the debugger could not evaluate.
ACTION Replace the mode expression with a valid numeric
expression.
UE388 MESSAGE Invalid expression for mode on "x" command
CAUSE The x (exit) command was given with an expression
for mode that the debugger could not evaluate.
ACTION Replace the mode expression with a valid numeric
expression.
UE390 MESSAGE Unknown name or command "CMD"
CAUSE Your command is not recognized by the debugger.
ACTION Enter a valid debugger command.
UE391 MESSAGE No playback name specified
CAUSE The file name is missing in a playback command.
ACTION Re-enter the playback command with a valid playback
file name.
UE392 MESSAGE Can't open FILE as playback file
CAUSE FILE does not exist or is unreadable.
ACTION Enter a valid file name, or change the file
permission if it exists already.
UE393 MESSAGE Can't open FILE as record file
CAUSE You don't have write permission in the specified
directory, or a non-writable file with the same
name already exists.
ACTION Enter a different file name, remove the old file,
or change the write permission for the directory.
UE394 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.
UE396 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.
UE397 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.
UE399 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.
UE400 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.
UE402 MESSAGE Can't take the address of a constant
CAUSE The operand of a &, $addr, or addr operator is
marked as a constant type.
ACTION Use the \t display format to find the type of the
operand.
UE403 MESSAGE Can't take the address of a register
CAUSE The operand of a &, $addr, or addr operator is
marked as a register type.
ACTION Use the \t display format to find the type of the
operand.
UE404 MESSAGE Prefix "++" not supported
CAUSE An attempt was made to use an unsupported ++ prefix
operator.
ACTION Make sure there is a space between a + and a unary
+ operator (for example 2+ +5). +=1 can be used to
increment.
UE405 MESSAGE Prefix "--" not supported
CAUSE An attempt was made to use an unsupported -- prefix
operator.
ACTION Make sure there is a space between a - and a unary
- operator (for example 2- -5). -=1 can be used to
decrement.
UE406 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.
UE407 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.
UE408 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.
UE409 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.
UE410 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
increment.