🚀 go-pugleaf

Can anyone tell me if there's a good way to trap the kinds of errors
that usually result in bombs?  I'm contemplating porting a debugger to
the ST, but a fundamental piece of functionality is the ability to use
my own trap vectors, or at least the get TOS to give control back to me
with a pointer to the crash data.  I would expect there to be some sort
of OS call for this, but haven't seen it.

Related question:  Does MUSHROOM.PRG work?  Whenever I run it it appears
to just dump a piece of the system stack, with no indication of the user
PC or failing instruction etc.  It then crashes itself with an
alignment error.  Is there a better substitute for MUSHROOM, or
documentation on where to find the crash data and how to interpret it?

Thanks.