Bug: deadlock from msyslog
hmurray at megapathdsl.net
Tue Mar 22 03:23:41 UTC 2016
esr at thyrsus.com said:
> I just ported in the Classic fix "[Bug 2814] msyslog deadlock when
> signaled." I think that'll do it for this one.
Is there any software that will check signal handlers to see if they call (or
call anything that calls) any non-signal-safe routines?
I don't know if it's possible to write real code following that rule. The
case I'm thinking of is a trap handler that catches a fatal error and wants
to print out a useful message and then exit somewhat cleanly. I think I'd be
willing to handle the hard cases by hand, or with as much help as I can get.
These are my opinions. I hate spam.
More information about the devel