Home
DevCentral
Search
Configure Global Search
Log In
Transactions
T628
Change Details
Change Details
Old
New
Diff
There is no legitimate reason SIGCHLD should be handled by the extension, so it shouldn't be intercepted. So, instead of `e4c_context_set_signal_mappings(e4c_default_signal_mappings);` in `mq_command` (and perhaps in `Rabbitmq_Unload` if extension unload code has been implemented), we should: # define our own signals array, with SIGSEGV, etc. but not SIGCHLD # call this array in `e4c_context_set_signal_mappings` instead of `e4c_default_signal_mappings` **Downstream workaround to cleanup** #Dæghrefn — When this bug is resolved, revert D111, which implements a workaround.
There is no legitimate reason SIGCHLD should be handled by the extension, so it shouldn't be intercepted. So, instead of `e4c_context_set_signal_mappings(e4c_default_signal_mappings);` in `mq_command` (and perhaps in `Rabbitmq_Unload` if extension unload code has been implemented), we should: # define our own signals array, with SIGSEGV, etc. but not SIGCHLD # call this array in `e4c_context_set_signal_mappings` instead of `e4c_default_signal_mappings` **Downstream workaround to cleanup** #Dæghrefn — When this bug is resolved, revert D111, which implements a workaround.
Continue