https://issues.apache.org/bugzilla/show_bug.cgi?id=49155

           Summary: mod_rewrite logging crashes apache 64 bit builds on
                    windows
           Product: Apache httpd-2
           Version: 2.2.15
          Platform: PC
        OS/Version: Windows Server 2008 (Longhorn)
            Status: NEW
          Severity: major
          Priority: P2
         Component: mod_rewrite
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Turning on mod_rewrite logging on 64 bit build of apache for windows crashes
apache when the first request comes in.

I have verified that turning on logging for mod_rewrite causes 64 bit httpd.exe
to crash on both Windows 7 64 bit and Windows Server 2008 R2 64 bit (tested
both 2.2.14 and 2.215 versions.)

Here is the fault from the Event Log:

Faulting application name: httpd.exe, version: 2.2.15.0, time stamp: 0×4b956fd9
Faulting module name: libapr-1.dll, version: 1.4.2.0, time stamp: 0×4b956f63
Exception code: 0xc0000005
Fault offset: 0×0000000000012b8a
Faulting process id: 0xb78
Faulting application start time: 0×01cad506a527eac9
Faulting application path: C:\Program Files\Apache Software
Foundation\Apache2.2\bin\httpd.exe
Faulting module path: C:\Program Files\Apache Software
Foundation\Apache2.2\bin\libapr-1.dll
Report Id: e5c38ca9-40f9-11df-97ea-00155d02b107

The mod_rewrite module does work. It’s only when turning on logging for it,
that the server crashes as soon as I try to access any resource:

#example
LoadModule rewrite_module modules/mod_rewrite.so
RewriteLog “C:/rewrite.log”
RewriteLogLevel 1

(Unfortunately, there is no official 64 bit build of Apache for windows.  The
build I used was from here: 
http://www.anindya.com/apache-http-server-2-2-15-x86-and-x64-windows-installers/)

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to