You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/12/10 00:59:04 UTC

DO NOT REPLY [Bug 25376] - Apache 2.0.48 & php 4.3.4 & AIX

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25376>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25376

Apache 2.0.48 & php 4.3.4 & AIX





------- Additional Comments From trawick@apache.org  2003-12-09 23:59 -------
We corresponded privately about a month ago and I believe you checked for ulimit
and coredumpdirectory and still couldn't get a core file generated.

The next best thing to get a backtrace for the segfault is to attach to a
running httpd process with the debugger, use the continue command to let the
httpd process run freely, then keep requesting the PHP page until the httpd
process you attached to segfaults.  Then get a backtrace.  Example:

gdb /path/to/httpd pid
(gdb) cont
[keep requesting the page until the debugger wakes up after SIGSEGV]
(gdb) where

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org