HP 3000 Manuals HP 3000 Manuals
What You See When a Trap Aborts a Process
The following sequence of events occurs when a process is aborted because
of a trap:
1. You see two messages (see Examples 1-1 and 1-2):
a. The first message indicates the error condition that caused
the abort.
b. The second message contains the program name and the type of
abort.
2. The JCW Job Control Word is set to indicate that an abort
occurred.
3. Depending on whether the SETDUMP intrinsic is armed, the following
happen:
a. If SETDUMP is not armed, then a minimal stack trace is
printed, and the process is terminated. This stack trace
contains all calls in which the destination (called) routine
is in a different executable library.
b. If SETDUMP is armed, the debugger is called with the SETDUMP
command string. Depending on the cause of the abort, the
debugger could be called again to allow interactive dialog.
Examples 1-1 and 1-2 illustrate a minimal (SETDUMP unarmed) and a full
(SETDUMP armed) stack trace, respectively:
____________________________________________________
| |
| |
| **** FILE NOT OPENED (PASCERR 706) |
| ABORT: MYPROG.GROUP.ACCT |
| SYS a.4147c TRAP_HANDLER+3c4 |
| XL 31.3361bc P__PASCFERROR+a0 |
| USER 30.30d8 proc_in_user_library+324 |
| PROG 25.4d30 proc_in_program+108 |
| |
____________________________________________________
Example 1-1: Minimal Stack Trace
_________________________________________________________
| |
| |
| **** FILE NOT OPENED (PASCERR 706) |
| ABORT: MYPROG.GROUP.ACCT |
| SYS a.4147c TRAP_HANDLER+3c4 |
| XL 31.361bc P__PASCFERROR+a0 |
| XL 31.30044 P__FERR+68 |
| XL 31.36a84 P_READINT+20 |
| USER 30.30d8 proc_in_user_library+324 |
| USER 30.54 first_proc_in_user_library+16 |
| PROG 25.4d30 proc_in_program+108 |
| PROG 25.8920 middle_proc_in_program+70 |
| PROG 25.234 first_proc_in_program+5c |
| PROG 25.f938 PROGRAM+94 |
| |
_________________________________________________________
Example 1-2: Full Stack Trace