quoted

quoted

Can you do anything at that time anyway? I mean, reset-all pending
either way.

You can boot a different kernel, or try to work out what went wrong.

No, I cant, all resources are possible busy.

That's a separate bug.  What resources do you see busy?  Allocated
memory, I/O devices?

Either way, maybe checking
what type stdout is and trap or exit depending on that.

That's better than always calling trap, sure.  Is there any reason
you can't just do it on Macs though?  Because the problem you're trying
to work around only happens there.

And I dont see whats bad about 'trap handler called', other than being
verbose.

Too verbose -- it prints useless information, and the actual error
message might scroll away.  No biggie of course, but why do the
workaround when not needed?


Segher