Why can't malloc be used in signal handlers? What can "happen wrong"?

A signal handler can be called at any time, including during times when another call to <code>malloc</code> is in progress. If this happens, one of two things will occur: <ol> <li>Your process will deadlock inside the signal handler, because <code>malloc</code> will be unable to acquire the heap lock.</li> <li>Your process will corrupt its heap, because <code>malloc</code> does acquire the lock (or doesn't think it needs it), then proceeds to render the heap inconsistent, leading to a later crash.</li> </ol>

Why is malloc not async signal safe?

1 Answers

A signal handler can be called at any time, including during times when another call to malloc is in progress. If this happens, one of two things will occur:

Your process will deadlock inside the signal handler, because malloc will be unable to acquire the heap lock.
Your process will corrupt its heap, because malloc does acquire the lock (or doesn't think it needs it), then proceeds to render the heap inconsistent, leading to a later crash.