DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=26799>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=26799 httpd process grows rapidly to > 1GB until server runs out of swap ------- Additional Comments From [EMAIL PROTECTED] 2004-03-21 11:55 ------- A log written by mod_log_forensic could be used to find all requests currently being processed by that child up to the point of the core. mod_log_forensic is in Apache 2.1-dev. You'll need the test_char.h file from 2.1-dev in order to compile it with Apache 2.0.x. I have stuck a copy at http://www.apache.org/~trawick/test_char.h in case you want to try that. mod_log_forensic is in 1.3.30-dev and 2.1-dev but not 2.0.50-dev yet. (Disclaimer: I've never tried to compile mod_log_forensic with 2.0.x, but I suspect it wouldn't be a big deal.) Alternately, mod_whatkilledus could be modified to dump information about all active connections/requests when a crash occurs, not just the connection/request on the thread that segfaulted. (See http://www.apache.org/~trawick/exception_hook.html.) I wouldn't mind at all making that enhancement (there would a config directive to tell it to dump info on each thread, not just the thread that crashed), but you need the exception hook capability in Apache 2.0.49 or Apache 2.1-dev to make that work. I don't know how to definitively determine each active request in a core dump without something like mod_whatkilledus, which keeps a table with a data structure per thread. But if a bit of guessing is fine, run strings on the core file and pick out all the request lines. Some subset of that would be the request lines of the requests currently being processed ;) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
