Edit report at http://bugs.php.net/bug.php?id=51580&edit=1
ID: 51580
Updated by: [email protected]
Reported by: marco at vmsoft-gbr dot de
Summary: socket_select randomly crashes when used together with
fork and Unix signals
-Status: Open
+Status: Feedback
Type: Bug
Package: PCNTL related
Operating System: Debian Linux
PHP Version: 5.3.2
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[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?
------------------------------------------------------------------------
[2010-04-17 03:51:06] [email protected]
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.