httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39513] New: - apache 1.3.35 - *** glibc detected *** double free or corruption (!prev) error on startup
Date Mon, 08 May 2006 16:35:03 GMT
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=39513>.
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=39513

           Summary: apache 1.3.35 - *** glibc detected *** double free or
                    corruption (!prev) error on startup
           Product: Apache httpd-1.3
           Version: HEAD
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: daviet@yahoo.com


Compiling apache 1.3.35 from source, using DSO: PHP/5.1.4, mod_gzip/1.3.26.1a, 
mod_perl/1.29, APC-3.0.10 

On RHEL 4, update 3 (latest), I receive this error:

Starting httpd: *** glibc detected *** double free or corruption (!prev): 
0x09bf74c0 *** 
/usr/local/apache/bin/apachectl: line 80: 25515 Aborted                 $HTTPD 
/usr/local/apache/bin/apachectl start: httpd could not be started 

On my 2 other systems running Fedora Core 5, I receive a similar error on one 
box and no error on the other box. Going back to Apache 1.3.34, the systems 
work fine. I have not had any similar issues with previous versions of Apache.

>From RedHat support:

The glibc version provided in the RHEL 4 performs some sanity checks to prevent 
data corruption. If a corruption is detected, a message similar to what you 
have received will be printed or logged, and the application causing the error 
will be killed.

You can find the details on this at the URL below (under the section glibc). 
There are also some tweaks suggested in the URL. You can tweak your OS at your 
own risk and Red Hat doesn't advice you to enable tweaks by default, nor do 
guarantee a solution by enabling these tweaks.

http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/as-
x86/

glibc
The version of glibc provided with Red Hat Enterprise Linux 4 performs 
additional internal sanity checks to prevent and detect data corruption as 
early as possible. By default, should corruption be detected, a message similar 
to the following will be displayed on standard error (or logged via syslog if 
stderr is not open):

*** glibc detected *** double free or corruption: 0x0937d008 ***

By default, the program that generated this error will also be killed; however, 
this (and whether or not an error message is generated) can be controlled via 
the MALLOC_CHECK_ environment variable. The following settings are supported:

0 — Do not generate an error message, and do not kill the program

1 — Generate an error message, but do not kill the program

2 — Do not generate an error message, but kill the program

3 — Generate an error message and kill the program

Note
If MALLOC_CHECK_ is explicitly set a value other than 0, this causes glibc to 
perform more tests that are more extensive than the default, and may impact 
performance.

Should you have a program from a third party ISV that triggers these corruption 
checks and displays a message, you should file a defect report with the 
application's vendor, since this indicates a serious bug.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message