Gossamer Forum
Home : Products : Gossamer Forum : Discussion :

Forum error after upgrading from RHEL3 to RHEL4

Quote Reply
Forum error after upgrading from RHEL3 to RHEL4
I get this problem after upgrading my development server OS from RHEL3 to RHEL4

This happens in error_log whenever I try to access any post.

*** glibc detected *** double free or corruption (!prev): 0x0a2e3478 ***

On my production server still running RHEL3, there is no problem. My database is hosted on the production server and the development server will connect to the database in production.

Strangely this problem still happens even if I do a fresh install of gforum on development while using the existing database. Is there any incompatibilty issue?

I am running Apache 1.3.33 on both machines.

Any help is appreciated.

Last edited by:

dauhee: Jul 6, 2005, 10:00 AM
Quote Reply
Re: [dauhee] Forum error after upgrading from RHEL3 to RHEL4 In reply to
An update. This is what I found in google.

man malloc
Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x)
include a malloc implementation which is tunable via environment vari-
ables. When MALLOC_CHECK_ is set, a special (less efficient) imple-
mentation is used which is designed to be tolerant against simple
errors, such as double calls of free() with the same argument, or
overruns of a single byte (off-by-one bugs). Not all such errors can
be protected against, however, and memory leaks can result. If MAL-
LOC_CHECK_ is set to 0, any detected heap corruption is silently
ignored; if set to 1, a diagnostic is printed on stderr; if set to 2,
abort() is called immediately. This can be useful because otherwise a
crash may happen much later, and the true cause for the problem is
then very hard to track down.

After I do
export MALLOC_CHECK_=1
most of the pages can now load except when listing out the individual thread titles in a forum. This page is still giving me the same error.