Dennis writes:
>
> Stan Sieler ([log in to unmask]) wrote:
> : Don asks:
> : > **** Unknown trap (TRAPS 69).
> : >
> : > ABORT: PGCMXFIX.PUB77.BETAMSS
> : > NM USER  454.00801084 U_get_unwind_table
> : > NM SYS  a.0021e098 px_getsig_lowpri_$1a8
> : >  --- Interrupt Marker
> : > NM SYS  a.00e0049c ?pi_call_2_handler_$8
> : >  --- Interrupt Marker
...
> Why not use: setdump ;debug="tr,i,d"?

If Dennis is asking in response to me suggestion using a breakpoint
at "trap_handler", it's because that's the only way to guarantee you
will catch/see the original trap.  Otherwise, if you rely on "setdump",
you see the trap ONLY if the program aborts.  If you have a trap handler
(e.g., xcodetrap / xaritrap / xsystrap, or a Posix signal handler),
the you might not be able to see the original trap point & information.
(E.g., the trap handler might have backed out of that area of the code,
and continued to run for awhile.)

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html