You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/05/25 00:56:05 UTC
DO NOT REPLY [Bug 29189] New: -
ap_log_error() with NULL server_rec lost after startup on Win32
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29189>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29189
ap_log_error() with NULL server_rec lost after startup on Win32
Summary: ap_log_error() with NULL server_rec lost after startup
on Win32
Product: Apache httpd-2.0
Version: 2.0-HEAD
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: mod_dav
AssignedTo: bugs@httpd.apache.org
ReportedBy: amorrow@nouveausystems.com
Calls to ap_log_error() with a NULL server_rec (as demonsrated by the DBG
macros in mod_dav.h) only appear in the error log during startup on Win32
while all such calls to ap_log_error() (both during startup and per-request)
appear in the error log on UNIX. On Win32, all calls to ap_log_error() with a
NULL server_rec after startup are lost.
This difference in the builds between UNIX and Win32 is a bug. They should
both behave the same.
One way to test this is to uncomment the usages of the DBG3 macro in
modules/dav/fs/repos.c . Using the standard builds for Win32 and UNIX, I find
that these calls produce output in the error log on UNIX but not on Win32.
The only workaround on Win32 I have found is to supply a non-NULL server_rec
in calls to ap_log_error() in per-request routines.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org