After two days of testing I can testify that Sorin's analysis is correct.
Sometimes Apache points to a user-agent string, sometimes it points to a null
string, and sometimes there is a null pointer.
The reason nothing appeared in the logs is because the requests coming in with
empty user-age
On 26/10/2021 08.18, miim wrote:
ua_pointer = apr_table_get(r->headers_in, "User-Agent");
/* Find out how long the Apache-supplied string is */
ualength = strlen(ua_pointer);
If the request does not contain any user-agent then ua_pointer will be
NULL. strlen of NULL will segfault.
My thanks to everyone for their input on this problem. While I was unable to
get the backtrace and whatkilledus modules to report on failure, I isolated the
cause to the following code in the handler.
The code itself does not segfault and indeed it appears to execute properly,
retrieving the
On 23/10/2021 02.49, miim wrote:
I have a relatively simple module which is nonetheless causing Apache to
intermittently segfault.
I've added debugging trace messages to be sent to the error log, but the lack of anything
in the log at the time of the segfault leads me to think that the error l
On Fri, Oct 22, 2021 at 8:49 PM miim wrote:
>
> I have a relatively simple module which is nonetheless causing Apache to
> intermittently segfault.
>
> I've added debugging trace messages to be sent to the error log, but the lack
> of anything in the log at the time of the segfault leads me to t
I have a relatively simple module which is nonetheless causing Apache to
intermittently segfault.
I've added debugging trace messages to be sent to the error log, but the lack
of anything in the log at the time of the segfault leads me to think that the
error log is not flushed when a message i
