HP 3000 Manuals HP 3000 Manuals
Chapter 46 Debug Low Level Breakpoint Management
(Subsystem 165)
--------------------------------------------------------------
---------------------------------------------------------------
5 MESSAGE This is an invalid address or caller has
insufficient capabilities to access it.
CAUSE The address validation routines detected an error
while checking the indicated address.
ACTION Check the address. If invalid, pass a valid
address. Remember to make sure the space ID for
long pointers is correct. If additional
capabilities are required, increase caller
capabilities or reduce protection on target
address.
---------------------------------------------------------------
10 MESSAGE This is an invalid BREAKPOINT INDEX; it is out of
range for valid BREAKPOINTS.
CAUSE The breakpoint index is out of range of valid
breakpoints.
ACTION Provide a valid breakpoint index.
---------------------------------------------------------------
15 MESSAGE The SINGLE STEP COUNT is invalid.
CAUSE A negative single step value was passed.
ACTION Provide a positive value.
---------------------------------------------------------------
20 MESSAGE An NM BREAKPOINT (not in the DEBUG TABLE) is at
that address.
CAUSE An NM breakpoint was found at the indicated
address. Since the breakpoint was not found in the
system debug tables, it must be a breakpoint from
some other subsystem or placed in the code by the
programmer.
ACTION Pick another location to set a DEBUG breakpoint
since DEBUG will not set a breakpoint on another
breakpoint.
---------------------------------------------------------------
25 MESSAGE The BREAKPOINT INDEX could not be found in the
BREAKPOINT TABLE.
CAUSE The breakpoint index specified is not in the
breakpoint tables.
ACTION List the current breakpoints and use an index of an
existing breakpoint.
---------------------------------------------------------------
30 MESSAGE A BREAKPOINT already exists at the indicated
address; can't set another.
CAUSE The caller tried to set an NM breakpoint where they
had already set one. Complete information about
the breakpoint existing at the location is returned
in the INFO parameter.
ACTION Pick a different place to set the NM breakpoint.
Delete the existing breakpoint and then set the new
one.
---------------------------------------------------------------
35 MESSAGE The BREAKPOINT is owned by another process; can't
clear it.
CAUSE The caller tried to delete an NM breakpoint which
he did not own.
ACTION Specify an NM breakpoint which the caller set.
Grant the user PM capabilities so they may delete
other people's breakpoints.
---------------------------------------------------------------
40 MESSAGE The DATA BUFFER is too small to hold the
indicated number of bytes.
CAUSE The user requested a data transfer that is larger
than the size of the passed buffer.
ACTION Increase the size of the buffer or request less
data.
---------------------------------------------------------------
45 MESSAGE A CM BREAKPOINT already exists at that address
(it's not in DEBUG TABLES!)
CAUSE A CM breakpoint was found at the indicated address.
Since the breakpoint was not found in the system
debug tables, it must be a breakpoint from some
other subsystem or placed in the code by the
programmer.
ACTION Pick another location to set a DEBUG breakpoint
since DEBUG will not set a breakpoint on another
breakpoint.
---------------------------------------------------------------
50 MESSAGE The procedure could not find the CM BREAKPOINT in
the BREAKPOINT TABLE; can't clear it.
CAUSE The CM breakpoint index specified is not in the
breakpoint tables.
ACTION List the current CM breakpoints and use an index of
an existing breakpoint.
---------------------------------------------------------------
55 MESSAGE There is a BREAKPOINT already set there.
CAUSE The caller tried to set a CM breakpoint where they
had already set one. Complete information about
the breakpoint existing at the location is returned
in the INFO parameter.
ACTION Pick a different place to set the CM breakpoint.
Delete the existing breakpoint and then set the new
one.
---------------------------------------------------------------
60 MESSAGE The END ADDRESS is bigger than START, or SIDs
don't match in DATA BREAK ADDRESS.
CAUSE The caller specified a range of address that cross
a space boundary or is not an ascending range.
ACTION Specify a correct address range.
---------------------------------------------------------------
65 MESSAGE The DATA BREAKPOINT INDEX could not be found in
the BREAKPOINT TABLE.
CAUSE The DATA breakpoint index specified is not in the
breakpoint tables.
ACTION List the current DATA breakpoints and use an index
of an existing breakpoint.
---------------------------------------------------------------
70 MESSAGE A DATA BREAKPOINT already exists somewhere in the
specified range; can't ARM.
CAUSE The caller tried to set a DATA breakpoint where
they had already set one. Complete information
about the breakpoint existing at the location is
returned in the INFO parameter.
ACTION Pick a different place to set the DATA breakpoint.
Delete the existing breakpoint and then set the new
one.
---------------------------------------------------------------
75 MESSAGE The DATA BREAKPOINT is owned by another process;
can't clear it.
CAUSE The caller tried to delete a data breakpoint which
he did not own.
ACTION Specify a DATA breakpoint which the caller set.
Grant the user PM capabilities so they may delete
other peoples' breakpoints.
---------------------------------------------------------------
85 MESSAGE The TARGET PIN is invalid or cannot be found in
the DEBUG TABLES.
CAUSE The system breakpoint PIN SYS_BP_PIN was specified
and is invalid for the desired function. Specified
PIN is not being monitored by the caller.
Specified PIN does not exist at all in the debug
tables.
ACTION Provide a correct PIN number.
---------------------------------------------------------------
90 MESSAGE The procedure could not find the PIN in
BREAKPOINT TABLE; can't ARM LOWER PRIV trap.
CAUSE A process attempted to stop at a place for which it
had insufficient capabilities. An attempt was made
to arm the LOWER PRIV trap, stopping the process at
the proper time. The trap could not be armed.
ACTION None.
---------------------------------------------------------------
95 MESSAGE No STATE found for the indicated PIN; can't ARM
the LOWER PRIV trap.
CAUSE A process attempted to stop at a place for which it
had insufficient capabilities. An attempt was made
to arm the LOWER PRIV trap, stopping the process.
The trap could not be armed.
ACTION None.
---------------------------------------------------------------
100 MESSAGE The maximum number of BREAKPOINTS for your
process has been reached.
CAUSE Each debug user is allowed a maximum fixed number
of breakpoints. That limit has been reached for
the calling process.
ACTION Delete some existing breakpoints.
---------------------------------------------------------------
105 MESSAGE You are not a DEBUG user (see the documentation
on how to use DEBUG routines).
CAUSE The caller has not identified himself as a debug
user by calling the debug_user_setup routine.
ACTION Call the debug_setup_user procedure.
---------------------------------------------------------------
110 MESSAGE You are not monitoring that PIN; can't
REMOVE/DISARM event.
CAUSE Probable cause is corruption of the internal debug
tables.
ACTION Kill all processes using DEBUG and retry the
desired operation. Reboot the system. Call your
Hewlett-Packard Representative if the problem
persists.
---------------------------------------------------------------
115 MESSAGE Your user must have PRIV capabilities for this
function.
CAUSE A request to perform an operation which required
the user to hav PM capabilities was issued.
Possibilities include: writing register data is
not allowed without PM; resuming execution at a new
location requires PM.
ACTION Grant the user PM capability.
---------------------------------------------------------------
120 MESSAGE You may not resume that PIN; someone else has
control over it.
CAUSE Same as for Message Content.
ACTION Provide a correct PIN number.
---------------------------------------------------------------
125 MESSAGE DEBUG cannot be run on this system; DEBUG system
start up code failed.
CAUSE Debug was not successfully initiated at system boot
time. It is not available.
ACTION Reboot the system. If the problem persists, call
your Hewlett-Packard Representative.
---------------------------------------------------------------
130 MESSAGE The procedure could not locate the DEBUGGER
GLOBAL DATA area.
CAUSE DEBUG could not allocate storage to maintain its
own local data storage. This could be due to lack
of disk space for virtual memory.
ACTION Verify that there is free virtual memory disk
space.
---------------------------------------------------------------
135 MESSAGE The actual INSTRUCTION for that address is not in
the BREAKPOINT TABLE.
CAUSE The indicated address does not exist in the debug
tables as an address where an NM breakpoint is set.
ACTION None.
---------------------------------------------------------------
140 MESSAGE The PIN is not accessible to you (not a CHILD or
you don't have PRIV mode).
CAUSE A PIN number was specified that is not a child of
the caller.
ACTION Grant the caller PM capabilities. Use a PIN that
is a child of the caller.
---------------------------------------------------------------
145 MESSAGE The procedure could not find the STATE
INFORMATION (ISM) for the indicated process.
CAUSE An interrupt marker (ISM) for the indicated PIN
could not be found in the debug tables. The ISM is
needed to alter a process's register state and to
arm the branch taken trap.
ACTION Make sure you are using the correct PIN number.
---------------------------------------------------------------
150 MESSAGE The procedure could not allocate the object
needed to store DEBUG GLOBAL DATA.
CAUSE VSM returned a bad status from a create_object call
made while initializing the debugger.
ACTION Make sure there is sufficient free disk space for
virtual memory.
---------------------------------------------------------------
155 MESSAGE This is an invalid PIN number; it is out of range
for the valid PINS.
CAUSE Same as message content.
ACTION Provide a valid PIN.
---------------------------------------------------------------
160 MESSAGE This address is inaccessible to you; insufficient
privilege or access rights.
CAUSE The VSM "probe" routine returned an error status.
This is caused by an undefined address or an
address to which the caller does not have access.
ACTION Make sure the address is valid.
---------------------------------------------------------------
165 MESSAGE The PIN was not found in the DEBUG TABLES; can't
RESUME the process.
CAUSE While trying to resume a process at a newly
specified address, the interrupt marker for the
process could not be located in the debug tables.
ACTION Call the resume routine without specifying a new
resume address.
---------------------------------------------------------------
170 MESSAGE The PIN is invalid; you may not specify your own
PIN.
CAUSE The caller's PIN was specified as the target of the
request function.
ACTION Specify a PIN other than your own.
---------------------------------------------------------------
175 MESSAGE SINGLE STEPPING is currently controlled by
another PIN; can set SS counter.
CAUSE An attempt was made to single step a process whose
single step counter is controlled by another
process.
ACTION Do not single step the process or try later when
the current owner of the single step counter is
finished with it.
---------------------------------------------------------------
180 MESSAGE The PIN was not found in the DEBUG TABLES; can't
set SS counter.
CAUSE While attempting to single step a process, the
process's interrupt marker could not be found in
the system debug tables.
ACTION None.
---------------------------------------------------------------
185 MESSAGE The DEBUG TABLES are full; try again later.
CAUSE The global system debug table is full.
ACTION Wait for the number of debug users to decrease.
Delete breakpoints, turn off traps (all these free
table space).
---------------------------------------------------------------
190 MESSAGE The indicated PIN does not exist.
CAUSE The indicated PIN did not exist when the request
was made.
ACTION Specify a valid PIN.
---------------------------------------------------------------
195 MESSAGE A compiler generated TRACE BREAKPOINT is already
set at that location.
CAUSE While attempting to set an NM breakpoint, one of
several compiler-generated breakpoints was found at
the indicated address.
ACTION Choose a different address at which to set the
breakpoint. Recompile the program without the
option that caused the special breakpoints to be
inserted. Relink the program, specifying the
";NODEBUG" option.
---------------------------------------------------------------
200 MESSAGE The TARGET PIN is invalid for the specified TRACE
event.
CAUSE The system breakpoint PIN was specified as the
target of the trace event request.
ACTION Use a PIN other than the system breakpoint PIN.
---------------------------------------------------------------
205 MESSAGE The TRACE event is currently owned by another
process; can't ARM it.
CAUSE The caller tried to set a trace event that has
already been set.
ACTION None.
---------------------------------------------------------------
210 MESSAGE The TRACE event is currently owned by another
process; can't DISARM it.
CAUSE The caller tried to disarm a trace event which he
did not own.
ACTION Specify a trace event which the caller set. Grant
the user PM capabilities so they may disarm other
peoples' trace events.
---------------------------------------------------------------
215 MESSAGE Invalid TRAP ID.
CAUSE An unknown or unsupported trap ID was specified.
ACTION Use a valid trap ID.
---------------------------------------------------------------
220 MESSAGE The trap is not currently ARMED.
CAUSE A request was made to disarm a trap that was not
armed.
ACTION Specify a trap that is armed.
---------------------------------------------------------------
225 MESSAGE The PIN was not found in the DEBUG TABLES; can't
ARM the trap.
CAUSE While attempting to arm a trap, the interrupt
marker for the specified process could not be found
in the debug tables.
ACTION None.
---------------------------------------------------------------
230 MESSAGE WARNING** The PIN was not found in the DEBUG
TABLES; can't clear T bit in PSW for PIN.
CAUSE While attempting to disarm a trap, the interrupt
marker for the specified process could not be found
in the debug tables.
ACTION None.
---------------------------------------------------------------
235 MESSAGE This trap is currently owned by another process;
can't ARM it.
CAUSE The caller tried to set a trace event that has
already been set.
ACTION None.
---------------------------------------------------------------
240 MESSAGE This trap is currently owned by another process;
can't DISARM it.
CAUSE The caller tried to disarm a trace event which he
did not own.
ACTION Specify a trace event which the caller set. Grant
user PM capabilities so they may disarm other
peoples' trace events.
---------------------------------------------------------------
245 MESSAGE You cannot set BREAKPOINTS on GATE instructions;
sorry.
CAUSE The address specified for an NM breakpoint
corresponds to a precision architecture gateway
page. Breakpoints may not be set on gateway pages.
ACTION None.
---------------------------------------------------------------
250 MESSAGE Dual BPs within the same node must have identical
count values.
CAUSE Another CM breakpoint was set that has a
corresponding translated NM breakpoint which maps
to the same NM node point. In such situations, the
breakpoint "COUNT" must be identical.
ACTION Provide the same COUNT value as the existing
breakpoint at the node point. Delete the existing
breakpoint before trying to set this one.
---------------------------------------------------------------
255 MESSAGE Dual BPs within the same node must have identical
comment strings.
CAUSE Another CM breakpoint was set that has a
corresponding translated NM breakpoint which maps
to the same NM node point. In such situations, the
breakpoint COMMAND STRING values must be identical.
ACTION Provide the same COMMAND STRING value as the
existing breakpoint at the node point. Delete the
existing breakpoint before trying to set this one.
---------------------------------------------------------------
260 MESSAGE An escape occurred while reading REGS from the
ISM.
CAUSE While trying to read/write register values to an
interrupt marker, an expected error was detected.
The result of the operation is undefined.
ACTION None.
---------------------------------------------------------------
265 MESSAGE Accessing NL.PUB.STS requires that you are in
PRIV mode.
CAUSE An attempt was made to access the system NL by a
user without PM capability.
ACTION Grant the user PM capability.
---------------------------------------------------------------
270 MESSAGE Accessing SL.PUB.SYS requires that you are in
PRIV mode.
CAUSE An attempt was made to access the system SL by a
user without PM capability.
ACTION Grant the user PM capability.
---------------------------------------------------------------
275 MESSAGE The actual CM INSTRUCTION for that address is not
in the breakpoint table.
CAUSE The indicated address does not exist in the debug
tables as an address where an CM breakpoint is set.
ACTION None.
---------------------------------------------------------------
280 MESSAGE A DATA BREAK TRP occurred which DEBUG did not
arm.
CAUSE Someone else has set a trap bit on a page in the
page table.
ACTION None.
---------------------------------------------------------------