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 is sent. For example, a segfault
occurs at 00:18:04, last previous request was at 00:15:36, so clearly the new
request caused the segfault. But not even the "Here I am at the handler entry
point" (see below) gets into the logfile before the server log reports a
segfault taking down Apache.
/* Retrieve the per-server configuration */
mod_bc_config *bc_scfg = ap_get_module_config(r->server->module_config,
&bridcheck_module);
if (bc_scfg->bc_logdebug & 0x0020000000000)
ap_log_rerror(APLOG_MARK, APLOG_NOTICE, 0, r,
"mod_bridcheck: Enter bridcheck_handler");
I could turn on core dumping but (a) I am no expert at decoding core dumps and
(b) I don't want to dump this problem on somebody else.
So ... is there a way to force Apache to flush the error log before proceeding?
