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=21322>. 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=21322 main worker process locks up and no longer accepts requests ------- Additional Comments From [EMAIL PROTECTED] 2003-07-12 19:46 ------- Okay, so this is really maybe two separate bugs that are interacting with each other. One is a bug in mod_include that is causing a segfault. The other is a failure to release a semaphore upon segv. Let's segregate the two issues. Can you open a second PR to track the mod_include problem? We'll leave this one open to look into the semaphore thing since it fits this job's summary already. In the new mod_include PR, please paste the backtrace with send_parsed_content () near the top, and please see if you can figure out for us what page was being served at the time of the segfault. I realize this may be difficult to do since the request would not yet have been logged at the time of the fault, but maybe through a little bit of induction you can figure out what page it was. See if you can reproduce the problem with a particular request reliably. Andre and I have been working on a triplet of mod_include bugs over the last three days or so -- this might be one of those or it might be a new one. (Probably a new one I think.) apr_bucket_delete() is a macro that calls APR_BUCKET_REMOVE() and apr_bucket_destroy(). Frame #1 being a function pointer would seem to indicate that it was apr_bucket_destroy() that failed (APR_BUCKET_REMOVE just manipulates a few pointers -- it doesn't call any functions). apr_bucket_destroy() is a macro that calls bucket->type->destroy() and bucket- >free(). It's hard to say which of those is the one that actually bombed. But in either case the most likely scenario is that we attempted to delete a bucket that had already been deleted. I'd have to see the file that mod_include was attempting to parse that caused the fault to know more. --Cliff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
