On 11/08/2011 11:30 AM, Rasmus Lerdorf wrote: > Not deferring SIGUSR2 just because valgrind on OSX doesn't like it isn't > really an option here. We could make debug builds on OSX not defer it, I > suppose.
I didn't want to imply we should change PHP behaviour in order to be valgrindable :) https://wiki.php.net/rfc/zendsignals is still listed as "Under discussion", but at least the signals listed under "Startup" are already registered it seems. I just learned that the various signals on Linux on Darwin have totally different numbers than on Linux, but $ valgrind /bin/bash shows the same behaviour as PHP, so I suspect it's really valgrind, as seen in memcheck/tests/sigkill.stderr.exp-darwin,92 in valgrind 3.7 source. I'm not directly able to see what they're doing different on OS X than on Linux, and if it makes sense at all - that's for someone with more expertise in C code review I guess :) Greetings, Florian -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
