Edit report at http://bugs.php.net/bug.php?id=51580&edit=1
ID: 51580
User updated by: marco at vmsoft-gbr dot de
Reported by: marco at vmsoft-gbr dot de
Summary: socket_select randomly crashes when used together with
fork and Unix signals
-Status: Feedback
+Status: Open
Type: Bug
Package: PCNTL related
Operating System: Debian Linux
PHP Version: 5.3.2
New Comment:
It doesn't crash in the literal sense, as I said before this was a
mistake in word choosing. So it's technically something other than a
crash, but I dunno how to properly call it. It's a bug, that's the only
thing thats sure.
Previous Comments:
------------------------------------------------------------------------
[2010-04-17 13:46:57] [email protected]
If it crashes then linux should be able to generate a core dump file
(without gdb). You can then use it to generate a back trace.
------------------------------------------------------------------------
[2010-04-17 13:39:33] marco at vmsoft-gbr dot de
Uh, the PHP *process* doesn't crash, so no corefile. Sorry, was bad
choice of words by me. Anyway, whatever happens with socket_select there
should not happen... but how to backtrace that one without an actual
crash?
------------------------------------------------------------------------
[2010-04-17 13:23:08] [email protected]
Can you try to generate a coredump and use it later to get a bt:
http://stackoverflow.com/questions/17965/generate-a-core-dump-in-linux
------------------------------------------------------------------------
[2010-04-17 11:13:18] marco at vmsoft-gbr dot de
just ran it under gdb, it fails as expected, but as it's not
segfaulting, no backtrace can be made.
------------------------------------------------------------------------
[2010-04-17 11:06:53] marco at vmsoft-gbr dot de
PHP itself doesn't crash, the error is not fatal - and how do I make a
gdb backtrace on a forked process, anyway?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=51580
--
Edit this bug report at http://bugs.php.net/bug.php?id=51580&edit=1
