Re: *** glibc detected *** double free or corruption RedHat 4 AS
- From: Michael Schwendt <mschwendt@xxxxxxxxx>
- Date: Fri, 13 Jun 2008 16:08:37 +0200
On Fri, 13 Jun 2008 07:44:55 -0500, mark wrote:
Bhat, Ajit wrote:
We always build our product on passing machine which is Linux 4 ES and
same code now testing on Linux 4 AS. Glibc and gcc version are different
on failing machine.
You built the program on one box, and then copied it to another box with a
Um, NOT a good idea.
Why? This is about RHEL 4, where glibc is the same for AS and ES.
Its version is still the same for several years. Just the patch-level
(= package release version) differs from the original RHEL4.
The stacktrace is not helpful, though, (at least not for an outsider)
because it doesn't even enter the application and because debuginfo is
missing. And, of course, it would be important to test against the
very latest glibc update from end of 2007, which is still the same
redhat-list mailing list
- Prev by Date: Re: *** glibc detected *** double free or corruption RedHat 4 AS
- Next by Date: Logrotate Question
- Previous by thread: Re: *** glibc detected *** double free or corruption RedHat 4 AS
- Next by thread: Logrotate Question