🚀 go-pugleaf

Under Aztec 3.6a, the ability to trap certain errors via a Unix-like "signal"
mechanism is provided.  Currently, illegal instruction, odd address and
divide by zero are supported.  I have tested these and they work.  A
cool thing about using them is that you can execute your cleanup routines,
thus turning what would be a visit to the guru into a well-behaved exit -- 
usually.  There's no guarantee that your rogue program hasn't trashed something
important prior to trapping.

Anyway, also, using signals seems to interfere with SDB.  I suppose SDB makes
use of illegal instructions for breakpoints and such.  The behavior is that
sdb says "program terminated normally" as soon as you return to sdb after
executing the signal init stuff.
-- 
-- "We've been following your progress with considerable interest, not to say
-- contempt."  -- Zaphod Beeblebrox IV
-- uunet!sugar!karl, Unix BBS (713) 438-5018