MPE/iX Error Messages Manual Vol 3 (32650-90880)

158 Chapter4
Error Messages Viii C 3
Symbolic Debugger
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