HP 3000 Manuals HP 3000 Manuals
User Errors (UE671 - UE785)
UE671 MESSAGE Invalid line number on "continue" command
CAUSE A line specified as part of a continue location is
out of range for the associated file.
ACTION Re-enter the command with a valid line number.
UE672 MESSAGE Invalid label on "continue" command
CAUSE A label specified as part of a continue location is
not known to the debugger.
ACTION Re-enter the command with a valid label name.
UE673 MESSAGE Invalid class on "continue" command
CAUSE A class specified as part of a continue location is
not known to the debugger.
ACTION Re-enter the command with a valid class name.
UE676 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.
UE677 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.
UE678 MESSAGE Invalid line number on "Continue" command
CAUSE A line specified as part of a continue location is
out of range for the associated file.
ACTION Re-enter the command with a valid line number.
UE679 MESSAGE Invalid label on "Continue" command
CAUSE A label specified as part of a continue location is
not known to the debugger.
ACTION Re-enter the command with a valid label name.
UE683 MESSAGE Invalid file on "view" command
CAUSE A file specified as part of a view 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.
UE684 MESSAGE Invalid procedure on "view" command
CAUSE A procedure specified as part of a view 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.
UE685 MESSAGE Invalid line number on "view" command
CAUSE A line specified as part of a view location is out
of the range of the associated file.
ACTION Re-enter the command with a valid line.
UE686 MESSAGE Invalid label on "view" command
CAUSE A label specified as part of a view location is not
known to the debugger.
ACTION Re-enter the command with a valid label name.
UE690 MESSAGE Invalid file on CMD command
CAUSE A file specified as part of a CMD 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.
UE691 MESSAGE Invalid procedure on CMD command
CAUSE A procedure specified as part of a CMD 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.
UE692 MESSAGE Invalid label on CMD command
CAUSE A label specified as part of a CMD location is not
known to the debugger.
ACTION Re-enter the command with a valid label name.
UE693 MESSAGE Invalid class on CMD command
CAUSE A class specified as part of a CMD location is not
known to the debugger.
ACTION Re-enter the command with a valid class name.
UE696 MESSAGE Must specify breakpoint to delete
CAUSE Although there is a breakpoint at the current
viewing location, a breakpoint number must be given
with the db (delete breakpoint) command.
ACTION Use the lb (list breakpoints) command to find the
number of the breakpoint you want to delete and
re-enter the db (delete breakpoint) command with
the breakpoint number.
UE697 MESSAGE Must specify function name
CAUSE The bpo (breakpoint overload) command was invoked
without a function name.
ACTION Re-enter the command with a function name.
UE698 MESSAGE Function not found
CAUSE No function matching the function name argument
given to the bpo (breakpoint overload) command was
found.
ACTION Re-enter the command with a valid function name.
Use the lp (list procedures) command to see a list
of all valid procedures.
UE709 MESSAGE Must specify breakpoint to suspend
CAUSE Although there is a breakpoint at the current
viewing location, a breakpoint number must be given
with the sb (suspend breakpoint) command.
ACTION Use the lb (list breakpoints) command to find the
number of breakpoints you want to suspend and
re-enter the sb (suspend breakpoint) command with
the breakpoint number.
UE710 MESSAGE Must specify breakpoint to activate
CAUSE Although there is a breakpoint at the current
viewing location, a breakpoint number must be given
with the ab (activate breakpoint) command.
ACTION Use the lb (list breakpoints) command to find the
number of breakpoints you want to activate and
re-enter the ab (activate breakpoint) command with
the breakpoint number.
UE726 MESSAGE Line not found in body of procedure
CAUSE There was an attempt to get the address of a line
using the notation function#line where line is not
in the body of the function.
ACTION Re-enter the expression with a valid function/line
number combination. Use the lp (list procedures)
command with the procedure's name. The range of
valid line numbers will be displayed with the
procedure.
UE729 MESSAGE Invalid structure access
CAUSE There was an attempt to use a non-pointer or a
pointer to a class member as a pointer, that is,
p->i where p is not of type pointer.
ACTION Re-enter the expression with a valid pointer, or
use the address of p if you need it, that is,
&(p)->i
UE731 MESSAGE Cannot assign to function
CAUSE There was an attempt to assign a value to a
function.
ACTION This is not supported by the debugger.
UE732 MESSAGE Nil character constant
CAUSE There was an attempt to use '' as a character.
ACTION Re-enter the expression with a valid character
constant. 'c', or '\value'
UE733 MESSAGE Invalid procedure given for "breakpoint trace"
command
CAUSE The debugger could not find a procedure with the
specified name.
ACTION Use the lp (list procedures) command to find what
procedures are known to the debugger, and
re-enter the command with the corrected name.
Alternatively, if the procedure you supplied was
not compiled with the debug flag, you can still set
a breakpoint at its entry point by using the 'ba
address' command.
UE734 MESSAGE Invalid procedure given for "bt" command
CAUSE The debugger could not find a procedure with the
specified name.
ACTION Use the lp (list procedures) command to find what
procedures are known to the debugger, and
re-enter the command with the corrected name.
Alternatively, if the procedure you supplied was
not compiled with the debug flag, you can still set
a breakpoint at its entry point by using the 'ba
address' command.
UE756 MESSAGE No registers in core file -- registers required
CAUSE The core file has a format not recognized by the
debugger.
ACTION Obtain a new core file on the same system as the
debugger you are running.
UE757 MESSAGE Modifier is not allowed before CMD command
CAUSE In cdb, fdb, or pdb, a modifier was entered before
a command that does not take a modifier.
ACTION Re-enter the command without a modifier in front of
it.
UE785 MESSAGE Address is required after "va"
CAUSE The va command was entered with no parameter.
ACTION Re-enter the command with an address argument.