#37793 [Com]: child pid xxx exit signal Segmentation fault (11)
| From: | g dot kunze at eyefi dot nl | Date: | Mon, 24 Aug 2009 08:43:59 +0000 |
| Subject: | #37793 [Com]: child pid xxx exit signal Segmentation fault (11) | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-141412@lists.php.net to get a copy of this message | ||
ID: 37793
Comment by: g dot kunze at eyefi dot nl
Reported By: niklas dot meyerson at natverkstan dot net
Status: No Feedback
Bug Type: Apache2 related
Operating System: Debian 2.6
PHP Version: 5.1.4
New Comment:
Ran into this bug while using Dwoo (see forum thread
http://forum.dwoo.org/viewtopic.php?pid=783).
The fact that this bug
makes PCRE functions fail silently (unless you happen to be looking at
your server logs) makes this bug quite severe.
Previous Comments:
------------------------------------------------------------------------
[2009-06-22 15:15:08] garyb at ivesinc dot com
This problem may just be due to a stack overflow. I suggest reading
comments on the bug report at pcre.org:
http://bugs.exim.org/show_bug.cgi?id=841.
Those comments also suggest
reading the 'pcrestack' man page.
------------------------------------------------------------------------
[2009-04-28 14:51:00] bugs dot php at cashers dot de
With regards to this bug report for preg_match which leads to segfault
errors in some cases, the solution is pretty simple. Just split the
string into smaller ones. E.g. with my xampp test server a length of
5000 is ok, but with 10000 chars it fails.
Just see the example which solves an encoding problem in adddition to
the preg_match bug: http://mobile-website.mobi/php-utf8-vs-iso-8859-1-59
------------------------------------------------------------------------
[2009-02-20 04:15:57] maddivenkatreddy at gmail dot com
Hi,
I am also getting the following error. Any one knows about this error
what is the route cause of this problem? and how to resolve it?
[Mon Feb 09 10:57:49 2009] [error] READ_TIMEOUT [os error=0, line 199
of ../nsapi/Reader.cpp]: no read after 3600 seconds
[Mon Feb 09 10:57:50 2009] [error] READ_TIMEOUT [os error=0, line 199
of ../nsapi/Reader.cpp]: no read after 3600 seconds
[Mon Feb 09 10:57:51 2009] [error] READ_TIMEOUT [os error=0, line 199
of ../nsapi/Reader.cpp]: no read after 3600 seconds
.
.
.
[Mon Feb 09 11:03:57 2009] [error] READ_TIMEOUT [os error=0, line 199
of ../nsapi/Reader.cpp]: no read after 3600 seconds
[Mon Feb 09 11:04:00 2009] [warn] child process 28307 still did not
exit, sending a SIGTERM
[Mon Feb 09 11:04:00 2009] [warn] child process 28308 still did not
exit, sending a SIGTERM
[Mon Feb 09 11:04:00 2009] [warn] child process 28309 still did not
exit, sending a SIGTERM
.
.
.
[Mon Feb 09 11:04:01 2009] [warn] child process 29235 still did not
exit, sending a SIGTERM
[Mon Feb 09 11:04:06 2009] [error] child process 29235 still did not
exit, sending a SIGKILL
[Mon Feb 09 11:04:22 2009] [notice] caught SIGTERM, shutting down
[Mon Feb 09 11:14:49 2009] [notice] Apache/2.0.52 (Unix) configured --
resuming normal operations
Thanks in Advance.
Venkat
------------------------------------------------------------------------
[2008-10-29 20:43:17] jeffs dot linux at gmail dot com
I am having this same error, my error code is as follows:
[Wed Oct 29 16:29:36 2008] [notice] child pid 18880 exit signal
Segmentation fault (11)
I traced it back to a preg_match function that opens up a file around
3.2KB and matches comment tags (its an html file). I am certain that it
has something to do with it because a die() function before it registers
but after it gives me a white errorless screen.
I dont know if the preg_match is the same issue, but it is certainly my
issue! The thing is I dont know how to get around this on... I might
need to change my approch.
------------------------------------------------------------------------
[2006-06-21 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
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/37793
--
Edit this bug report at http://bugs.php.net/?id=37793&edit=1