In reference to bug 20462 I see you are tracking down the root cause of this problem. In doing some tracking on Windows with 2.0.47 I came up with a check that prevents the crash, though it doesn't by any means solve the bigger issue you are working on.
My description of problem before seeing issue 20462: While apache is shutting down a write to a file fails because the mutex value has been cleaned up. It then tries to log this error to an error log file but the file handle has been invalidated by this time. The fix adds a simple check for a valid file handle before trying to call the function apr_thread_mutex_lock() which needs a valid file handle and mutex or it crashes. File: httpd-2.0/srclib/apr/file_io/win32/readwrite.c Function: apr_file_write If you think this would be of any assistance I can send the code change to you David Blake Venturi Technology Partners (HP-Boise Location) -----Original Message----- From: Bill Stoddard [mailto:[EMAIL PROTECTED] Sent: Thursday, December 11, 2003 2:57 PM To: [EMAIL PROTECTED] Subject: Re: [PATCH] Create plog pool before pconf William A. Rowe, Jr. wrote: > So you propose an inversion here? Won't that break as many modules making > the (currently) correct assumptions, w.r.t. config data? > > Logs are created *from* values in the configuration, ergo they should go away > *before* the values that created them are also destroyed. > > E.g., if my module creates a log file, and points at the name of that log, then > the name of that log cannot become invalid before that log file is destroyed > and cleared. > > Bill Yea, I woke up this morning thinking about this. This patch stands to break more than it fixes and it certainly breaks precedence. I suspected as much which is why I posted the patch. Thanks for the comments. -1 Bill
