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/08/05 16:18:40 UTC
DO NOT REPLY [Bug 22137] -
unknown segfault in worker MPM child process
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=22137>.
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=22137
unknown segfault in worker MPM child process
trawick@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|perform idle server |unknown segfault in worker
|maintenance core dump |MPM child process
------- Additional Comments From trawick@apache.org 2003-08-05 14:18 -------
The portion of the backtrace showing idle server maintenance ran in the parent
process prior to fork()-ing this child.
This backtrace is from the child. The backtrace is for the main thread of the
child, which sits in read() until the parent tells it to go away.
Either we don't have the backtrace for the thread that segfaulted (> 99.99%
chance) or Solaris read() is broken. read() is responsible for returning EFAULT
if passed an invalid buffer, so this backtrace isn't consistent with any likely
segfault.
See what other backtraces are in the coredump. Also, the Solaris pflags program
often identifies the thread that segfaulted.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org