httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53329] Segmentation fault in ap_escape_logitem() method
Date Mon, 25 Jun 2012 17:02:43 GMT

Jeff Trawick <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #12 from Jeff Trawick <> ---
(In reply to comment #10)
> My problem got resolved. It turned out to be one of the modules that we have
> written causing the problem. I have disabled that module and that did the
> trick. Actully, the same module was running fine with 2.2.9 so that made me
> curious what got changed that causing the issue.
> Remember, i had also mentioned that i had lots of wiered entries in the logs
> in the first column (where it supposed to show remote client IP?). So when i
> checked the mod_log_config.c, it seems one option had been added (-k) which
> was not there in 2.2.9 and some how that's causing conflict with our custom
> module. 
> By the way, custome module was changing the remote ip to one we are passing
> through config for security reason. But we have used work around and disable
> that plug-in.

Maybe a conn_rec was created by the custom module and allocated from the wrong

At any rate this is apparently not an httpd bug.

> Thanks Stefan for acknowledging that "wiered log entries could lead to
> Segmentation error".
> I think we could have resolved the issue by increasing length for below
> mentioned two parameters, but that needs rebuilding of Apache - 
> LimitRequestFieldSize
> LimitRequestLine
> Hope, that helps to some one who are facing such issues given the similar
> situation!

Unclear.  The problem doesn't occur without the custom code, and others
probably won't have that custom code.

If you find out the root cause (exactly what in the custom module led to the
problem), update the bug in case it can help others.

> Thanks
> Maulik

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message