Bug #37793 [Com]: child pid xxx exit signal Segmentation fault (11)

From: Date: Mon, 12 Nov 2012 10:41:34 +0000
Subject: Bug #37793 [Com]: child pid xxx exit signal Segmentation fault (11)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-174637@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=37793&edit=1

 ID:                 37793
 Comment by:         kevin at vanzonneveld dot net
 Reported by:        niklas dot meyerson at natverkstan dot net
 Summary:            child pid xxx exit signal Segmentation fault (11)
 Status:             No Feedback
 Type:               Bug
 Package:            Apache2 related
 Operating System:   Debian 2.6
 PHP Version:        5.1.4
 Block user comment: N
 Private report:     N

 New Comment:

This report says 'Apache related', but we ran into this running an old Horde 
version from CLI trying to import emails (some spam mails trigger the bug and 
crash the importer).

Horde 'solved' their problem like so: 
https://github.com/horde/horde/commit/7053f7ae

It puzzles me how a serious bug like this, causing Segmentation Faults, could have 
been in PHP since 2006 without any attempts to fix.


Previous Comments:
------------------------------------------------------------------------
[2011-05-13 08:43:49] yasanthau at yahoo dot com

I'm also getting the same error. I installed torrentflux_2.4 on a fresh Centos 5.5 server with
apache 2.2

The login screen appears on torrentflux. But when I login after putting username and password,
"page cannot be displayed" error comes on browser and following errors on apache error
log.

[Fri May 13 17:21:58 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri May 13 17:21:58 2011] [notice] Digest: generating secret for digest authentication ...
[Fri May 13 17:21:58 2011] [notice] Digest: done
[Fri May 13 17:21:58 2011] [notice] mod_python: Creating 4 session mutexes based on 256 max
processes and 0 max threads.
[Fri May 13 17:21:58 2011] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
[Fri May 13 17:22:07 2011] [notice] child pid 25314 exit signal Segmentation fault (11)
[Fri May 13 17:22:10 2011] [notice] child pid 25316 exit signal Segmentation fault (11)

Googled so much and no fixes works for me

Thanks

------------------------------------------------------------------------
[2010-02-16 06:19:19] jbd at pbptech dot com

Hi, 

I am running OpenBSD 4.6 and recently updated the php package to 5.2.10.

Since then i am also receiving the same errors as above.

All I have in my test file is

<?php

  session_start();
  echo "OK";

?>

After reloading the page several times, it will fail every now and then with a segfault in the
Apache/1.3.29 server error_log.

PHP Info is here: http://pbp.no-ip.com/info.php
Test File is here: http://pbp.no-ip.com/segfault.php

Thank you.

------------------------------------------------------------------------
[2009-08-24 08:43:58] g dot kunze at eyefi dot nl

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.

------------------------------------------------------------------------
[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

------------------------------------------------------------------------


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

    https://bugs.php.net/bug.php?id=37793


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=37793&edit=1


Thread (9 messages)

« previous php.bugs (#174637) next »