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=39914>. 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=39914 Summary: crash in ap_log_rerror() from jk_log_to_file() Product: Tomcat 5 Version: 5.5.16 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Native:JK AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] mod_jk-1.2.15, httpd-2.0.52 with RH ES4 patches applied running on RH ES4 update 3. I haven't figured out what the root cause of this is: jk_log_lock doesn't appear to get initialized, so both the lock and the unlock fail with EINVAL (presumably coming from pthread_mutex_{lock,unlock} ()). The unlock error case calls ap_log_rerror() with a NULL request pointer, but this routine dereferences the pointer immediately to pick up the server information, causing a core dump. I changed it to ap_log_error() and that fixes the crash. I still don't know why the mutex is not initialized; I can only assume that the post config hook is not being called or is failing for some reason. Let me know if any further information is needed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
