On Fri, Oct 26, 2012 at 12:36:41PM -0700, Ethan Jackson wrote:
> Occasionally, backtrace() will deadlock in the signal handler
> because it does some non signal safe initialization. Specifically,
> it opens a shared object. As a work around, this patch forces
> backtrace() to run outside of a sig
Occasionally, backtrace() will deadlock in the signal handler
because it does some non signal safe initialization. Specifically,
it opens a shared object. As a work around, this patch forces
backtrace() to run outside of a signal handler, so that future
calls will perform as expected.
Signed-off
