The bug is for mod_jk, not jk2. We use sprintf there, and that is probably the problem.
If we can get a stack trace we can easily find the offending log() and add a check for null. I'll add a small macro and start adding it to all log(), to be sure. Costin On Fri, 14 Jun 2002, GOMEZ Henri wrote: > Very strange behaviour. > > I didn't understand why the log cause a segv when JkLogLevel > is in INFO mode, whereas there is less log activity. > > It could be in jk_log, or all others *printf routines. > > Did ap_psprintf is used to core with %s and NULL string > passed ? > > > >-----Original Message----- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > >Sent: Thursday, June 13, 2002 8:04 AM > >To: [EMAIL PROTECTED] > >Subject: DO NOT REPLY [Bug 6457] - mod_jk causes segmentation > >fault with > >JkLogLevel != debug > > > > > >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=6457>. > >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=6457 > > > >mod_jk causes segmentation fault with JkLogLevel != debug > > > > > > > > > > > >------- Additional Comments From [EMAIL PROTECTED] > >2002-06-13 06:03 ------- > >Can you send a stack trace ( gdb httpd core, then bt ) ? > > > >This is most likely due to a printf(%s) with null argument, > >jk2 has replaced > >all calls to APR equivalent. > >I'll do a search on the source and check the log statements. > > > >-- > >To unsubscribe, e-mail: > ><mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: > ><mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
