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

Chapter 4 157
Error Messages Viii C 3
Symbolic Debugger
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.