Mikael Djurfeldt <[EMAIL PROTECTED]> writes:
> But, as you previously suggested, it is not sensible to try to
> continue executing code after a segv. That *kind* of signals should
> cause immediate abort, I think.
I think which signals belong to "That *kind* of signals" should be
application specific:
I use guile to interactively control a pci-to-vme bridge that gives
SIGBUS in a lot of non-fatal situations: vme-crate is not switched on,
no data available in fifo of a vme-card etc. I guess using SIGBUS for
that purpose is a bad design choice, but the device driver is outside
my control.
Regards, Ole
