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=20421>. 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=20421 child pid $PID exit signal Segmentation fault (11) ------- Additional Comments From [EMAIL PROTECTED] 2003-06-05 13:00 ------- The situation "And the crash does seem to happen inside Apache anyway.." is just the normal situation where PHP module for Apache has a problem. There may be some confusion because the backtrace you got from gdb is for the first thread of a worker MPM child process, which always sits in read() until shutdown. That isn't the thread that segfaulted. See if more than one core dump was written (some levels of Linux write out one for the main process and one for the thread that puked) or if gdb will display info for other threads in that coredump. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
