Thanks but same application runs on Linux 4 ES? Stack trace is - #0 0x0000003468f2e21d in raise () from /lib64/tls/libc.so.6 (gdb) where #0 0x0000003468f2e21d in raise () from /lib64/tls/libc.so.6 #1 0x0000003468f2fa1e in abort () from /lib64/tls/libc.so.6 #2 0x0000003468f63291 in __libc_message () from /lib64/tls/libc.so.6 #3 0x0000003468f686b2 in malloc_consolidate () from /lib64/tls/libc.so.6 #4 0x0000003468f68c3a in _int_free () from /lib64/tls/libc.so.6 #5 0x0000003468f691f6 in free () from /lib64/tls/libc.so.6 #6 0x0000003468f30c69 in exit () from /lib64/tls/libc.so.6 #7 0x0000003468f1c402 in __libc_start_main () from /lib64/tls/libc.so.6 #8 0x0000000000584a8a in _start () http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-note s/as-x86/ - Ajit -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Michael Schwendt Sent: 13 June 2008 12:04 To: redhat-list@xxxxxxxxxx Subject: Re: *** glibc detected *** double free or corruption RedHat 4 AS On Fri, 13 Jun 2008 11:57:15 +0100, Bhat, Ajit wrote: > Hi - > > We are getting core dumps at exit on Linux 4 AS, Same application runs > successfully on Linux 4 ES > > The error we receive on Linux 4 AS is - > *** glibc detected *** double free or corruption (!prev) > > Following link discusses work around > http://www.redhat.com/docs/manuals/e...-notes/as-x86/ > > wondering if this is a bug in glibc. How do we resolve this? Is it by > upgrading glibc? It is much more likely a bug in the application. Show the stacktrace. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
