#21756 [Opn->Fbk]: Accessing $_SERVER['PATH_INFO '] causes intermittent segfault in Apache

From: Date: Fri, 02 May 2003 01:36:49 +0000
Subject: #21756 [Opn->Fbk]: Accessing $_SERVER['PATH_INFO '] causes intermittent segfault in Apache
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-38924@lists.php.net to get a copy of this message
ID: 21756 Updated by: sniper@php.net Reported By: php at lost dot co dot nz -Status: Open +Status: Feedback Bug Type: Apache related Operating System: Linux/Apache (Debian 3.0r1) PHP Version: 4.3.0 New Comment: Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip Previous Comments: ------------------------------------------------------------------------ [2003-04-23 21:28:33] flight553 at yahoo dot com Change your configure statement to '--enable-discard-path' and then PHp will not try to fopen whatever the PATH_INFO is. ------------------------------------------------------------------------ [2003-02-06 16:59:05] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip With the very little information you've given..please give the snapshot a try. If the problem persists, please give us a _complete_ and short example script which can be used to reproduce this. Also, what was the configure line used to configure PHP? ------------------------------------------------------------------------ [2003-02-06 13:36:56] php at lost dot co dot nz I have already tried to generate the requested backtrace (as already noted below...), but was unable to get apache to segfault while I was watching. I determined the cause of the bug by comparing access and error logs, looking at the called scripts, and examining points of similarity. The bug was confirmed when, after I wrapped the reads to $_SERVER['PATH_INFO'] (see below) the segfault frequency went from 1-200/day to zero. This was the only change made, which would seem to clinch the deal. ------------------------------------------------------------------------ [2003-02-04 16:51:06] sniper@php.net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2003-01-20 04:50:25] sniper@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. There you can find some info how to use GDB properly. Can you provide a short, COMPLETE and self-contained example script that can be used to reproduce this? It's not much use for us to try guessing unless you don't give us the necessary information.. ------------------------------------------------------------------------ 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/21756 -- Edit this bug report at http://bugs.php.net/?id=21756&edit=1

« previous php.bugs (#38924) next »