|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2003-06-23 21:29 UTC] sniper@php.net
[2003-06-30 03:32 UTC] wez@php.net
[2003-06-30 05:51 UTC] sniper@php.net
[2004-03-08 17:01 UTC] joseph at serengeti dot com
[2004-03-09 02:00 UTC] hessu at hes dot iki dot fi
[2004-03-09 07:25 UTC] sniper@php.net
[2004-03-09 08:01 UTC] hessu at hes dot iki dot fi
[2004-03-09 08:14 UTC] sniper@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Thu Oct 30 15:00:01 2025 UTC |
Description: ------------ php-4.3.2 and php4-STABLE-200306231730 on apache-2.0.46, RedHat Linux on i386, vanilla 2.4.20 kernel, gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7). When trying to send a binary or ascii file of exactly 65536 bytes using readfile() or fpassthru(), the httpd process dies with a SIGSEGV. If the file is 65535 or 65537 bytes long, it is sent out just fine. 32768 and 131072 bytes do not seem to crash, either. The same source file does not crash the command line version of php. Reproduce code: --------------- $ cat 64kcrash.php <? readfile("64k-of-data"); ?> $ $ dd if=/dev/urandom of=64k-of-data bs=1 count=65536 OR $ perl -e 'print "a" ? 65536;' > 64k-of-data Expected result: ---------------- The contents of the file should be sent. Actual result: -------------- [Mon Jun 23 22:46:56 2003] [notice] child pid 7805 exit signal Segmentation fault (11) client gets EOF after sending the request.