php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #32971 SIGPIPE Broken Pipe, occurs on one of two machines
Submitted: 2005-05-06 22:16 UTC Modified: 2005-05-09 09:21 UTC
From: saeven at saeven dot net Assigned:
Status: Not a bug Package: Scripting Engine problem
PHP Version: 5.0.4 OS: Fedora Core 2
Private report: No CVE-ID: None
 [2005-05-06 22:16 UTC] saeven at saeven dot net
Description:
------------
Inclusion of a custom user session object at a particular point causes segmentation faults.  Occurs in both Zend optimized and un-optimized code.

Works on several machines, but fails on a distinct few as well.  Apache as well as PHP have been recompiled.

Help interpreting the stack trace would be appreciated.

Actual result:
--------------
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread -1208590208 (LWP 15537)]
0x0060d7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0 0x0060d7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x006d9eac in writev () from /lib/tls/libc.so.6
#2 0x08073fb9 in ssl_io_hook_writev ()
#3 0x080ac402 in ap_hook_call_func ()
#4 0x080abbea in ap_hook_call ()
#5 0x080884c4 in writev_it_all ()
#6 0x08088859 in large_write ()
#7 0x0808891c in ap_bwrite ()
#8 0x0809beee in ap_rwrite ()
#9 0x0030b9a3 in ?? () from /usr/local/apache/libexec/libphp5.so
#10 0x002c6b8b in ?? () from /usr/local/apache/libexec/libphp5.so
#11 0x002c6bf9 in ?? () from /usr/local/apache/libexec/libphp5.so
#12 0x002c5dfe in ?? () from /usr/local/apache/libexec/libphp5.so
#13 0x002e8639 in ?? () from /usr/local/apache/libexec/libphp5.so
#14 0x002e85df in ?? () from /usr/local/apache/libexec/libphp5.so
#15 0x002e8130 in ?? () from /usr/local/apache/libexec/libphp5.so
#16 0x00b13849 in get_module () from /usr/local/Zend/lib/Optimizer-2.5.7/php-5.0.x/ZendOptimizer.so
#17 0x00b79738 in ?? () from /usr/local/Zend/lib/Optimizer-2.5.7/php-5.0.x/ZendOptimizer.so
#18 0x003956f4 in ?? () from /usr/local/apache/libexec/libphp5.so
#19 0x00b134a0 in get_module () from /usr/local/Zend/lib/Optimizer-2.5.7/php-5.0.x/ZendOptimizer.so
#20 0x00b7c6e0 in ?? () from /usr/local/Zend/lib/Optimizer-2.5.7/php-5.0.x/ZendOptimizer.so
#21 0xbfe1caf8 in ?? ()
#22 0xbfe1cb38 in ?? ()
#23 0x00b79738 in ?? () from /usr/local/Zend/lib/Optimizer-2.5.7/php-5.0.x/ZendOptimizer.so
#24 0x00b7c6e0 in ?? () from /usr/local/Zend/lib/Optimizer-2.5.7/php-5.0.x/ZendOptimizer.so
#25 0xbfe1caf8 in ?? ()
#26 0x00000000 in ?? ()

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-05-07 03:29 UTC] wez@php.net
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

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.

your stack trace is not useful for two reasons:
- you need to build a debug build of PHP (which means running without the zend optimizer)
- gdb will catch signals like SIGPIPE that are otherwise handled by the program being debugged.  You can either tell gdb to "cont" when you see that message, or create a .gdbinit file that has "handle SIGPIPE nostop" in it.
 [2005-05-09 02:10 UTC] saeven at saeven dot net
Hi,

  Having compiled with --enable-debug, being forced then to use the unencoded version, the problem no longer occurs.  The bug then safely can be assumed to be with Zend Optimizer?  Where should I direct a Zend Optimizer bug report?

Thanks!
Alex
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Sep 18 22:01:26 2024 UTC