ID:               21756
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Open
+Status:           Feedback
 Bug Type:         Reproducible crash
 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


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?



Previous Comments:
------------------------------------------------------------------------

[2003-02-06 13:36:56] [EMAIL PROTECTED]

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] [EMAIL PROTECTED]

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] [EMAIL PROTECTED]

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


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

[2003-01-20 04:46:57] [EMAIL PROTECTED]

Yes, you're right, the include() statement in my toy example should
have been wrapped in a pair of braces - the actual code does not
contain calls to include() however...

I'm sorry I could not provide a backtrace - the thing refused to
misbehave when gdb was listening.  Prehaps someone who is more familiar
with the Apache (1.3) / PHP interface will know where to examine more
closely.

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

[2003-01-20 00:04:35] [EMAIL PROTECTED]

Sounds pretty unlikely for the crash being caused 
by unset variable/array index. 

And btw. If you conditionally include() files, then
you MUST use { } with the clauses:

http://www.php.net/manual/en/function.include.php
(Example 12-6)

Maybe this caused the crashes?



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

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

Reply via email to