Guardian Procedure Errors and Messages Manual

Cause This error occurs for one of the following reasons:
• A page fault occurred, but no physical memory page is available for overlay.
• Disk space cannot be allocated when the program is referencing an extensible segment.
Effect For trap 12, process control passes to the Debug or Inspect debugger or to the trap handler
designated by a call to the ARMTRAP procedure, or else the process is abended. For more
information, see “Trap Handling” (page 273).
For the signal SIGNOMEM, the default or specified signal handling occurs. For more information,
see “Signal Handling” (page 274).
Recovery If the program was using extensible segments, either free up disk space on the swap
volume or specify a swap file on a different volume.
SIGMEMERR, Trap 13 Uncorrectable memory error
Cause An uncorrectable memory error occurred.
Effect For trap 13, process control passes to the Debug or Inspect debugger or to the trap handler
designated by a call to the ARMTRAP procedure, or else the process is abended. For more
information, see “Trap Handling” (page 273).
For the signal SIGMEMERR, the default or specified signal handling occurs. For more information,
see “Signal Handling” (page 274).
Recovery If possible, rerun your application. Otherwise, contact your system manager.
SIGABRT (No trap) Abnormal termination
Cause A procedure running within the process called abort() or raise(SIGABRT).
Effect For the signal SIGABRT, the default or specified signal handling occurs. For more information,
see “Signal Handling” (page 274).
Recovery Recovery is application dependent.
SIGALRM (No trap) Timer expiration
Cause A procedure called alarm() and the specified time has elapsed.
Effect For the signal SIGALRM, the default or specified signal handling occurs. For more information,
see “Signal Handling” (page 274).
Recovery Recovery is application dependent. It is possible to resume from SIGALRM and to continue
the program from the site of the interruption.
Error Lists
If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem,
you might receive a trap-out error list in a response. HP subsystems return such an error list when,
in performing your request, they encounter either a trap condition or an exception condition that
causes a signal to be generated.
Each error list always includes the unconditional tokens listed under its description. If you are
designing a subsystem that uses SPI, include all unconditional tokens listed in the error list's
description.
This subsection does not discuss the mechanics of error-list construction. For information about
creating error lists, for additional information about tokens and token types, and for definitions of
tokens whose names begin with ZSPI-, see the SPI Programming Manual.
278 Traps and Signals