Hi - 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. - Ajit -----Original Message----- From: Bhat, Ajit Sent: 13 June 2008 12:29 To: 'General Red Hat Linux discussion list' Subject: RE: *** glibc detected *** double free or corruption RedHat 4 AS Thanks - Architecture on both machine is exact same, but are differences in glibc version rpm -q -a | grep glibc On failing machine - glibc-2.3.4-2.25 glibc-devel-2.3.4-2.25 glibc-kernheaders-2.4-9.1.98.EL glibc-2.3.4-2.25 glibc-devel-2.3.4-2.25 compat-glibc-2.3.2-95.30 glibc-utils-2.3.4-2.25 glibc-common-2.3.4-2.25 compat-glibc-headers-2.3.2-95.30 glibc-headers-2.3.4-2.25 glibc-profile-2.3.4-2.25 compat-glibc-2.3.2-95.30 On passing machine - glibc-2.3.4-2 glibc-kernheaders-2.4-9.1.87 glibc-devel-2.3.4-2 glibc-2.3.4-2 glibc-headers-2.3.4-2 glibc-common-2.3.4-2 glibc-devel-2.3.4-2 I am not sure why they are not same, but will that make difference? Also, that's the only stack trace we get which is not much informative. - Ajit -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Michael Schwendt Sent: 13 June 2008 12:22 To: redhat-list@xxxxxxxxxx Subject: Re: *** glibc detected *** double free or corruption RedHat 4 AS On Fri, 13 Jun 2008 12:09:04 +0100, Bhat, Ajit wrote: > Thanks but same application runs on Linux 4 ES? Memory deallocation corruption can depend on memory usage, stack usage, other run-time side-effects. Is it the same architecture (x86_64) on both installations? Same version of glibc? If not, why not? And in either case, which version of glibc is it? > 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 () Not sure this is correct. What application do you refer to? -- 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
