Skip to content

Conversation

mickael9
Copy link
Contributor

@mickael9 mickael9 commented Jan 9, 2016

When an fpm child handles more than one request, zend_signal_startup() will override the saved signal handlers with the internal zend handlers set from the previous request, causing a SIGQUIT signal to result in a core dump rather than gracefully exiting (the expected behaviour).

This is fixed by adding a call to zend_signal_init() after setting the signal handlers in the child. The same technique is used in the apache SAPI module in commit fd5a756 which addresses bug #61083.

This addresses bug #71269.

When an fpm child handles more than one request, zend_signal_startup() will
override the saved signal handlers with the internal zend handlers set from the
previous request, causing a SIGQUIT signal to result in a core dump rather than
gracefully exiting (the expected behaviour).

This is fixed by adding a call to zend_signal_init() after setting the
signal handlers in the child. The same technique is used in the apache SAPI
module in commit fd5a756 which addresses
bug #61083.
@laruence laruence added the Bug label Jan 14, 2016
@kkkrist
Copy link

kkkrist commented Feb 3, 2016

Just out of curiosity (and lack of knowledge most probably): Is there a reason this has not been merged yet?

@ShadowNinja
Copy link

This issue affects me, and this patch seems like it's a pretty trivial bugfix.

@buchdag
Copy link

buchdag commented Feb 14, 2016

I'm affected by this issue too.

@numbleroot
Copy link

Experiencing the same core dump. Please merge this.

@php-pulls php-pulls merged commit b0780d3 into php:master Feb 15, 2016
@laruence
Copy link
Member

merged, thanks for the fixing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants