HP 3000 Manuals HP 3000 Manuals
User Errors (UE300 - UE416)
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 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
(31508-90003) 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
(31508-90003) 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
(31508-90003) 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 (31508-90005) 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 (31508-90005) 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 (31508-90003) 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
(31508-90003) 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
(31508-90003) 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
(31508-90003) 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
(31508-90003).
---------------------------------------------------------------
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.
---------------------------------------------------------------