"Bhat, Ajit" <abhat@xxxxxxxxxxxxxxx> writes: > We recently upgraded compiler from to 3.4.3. > We are facing core dumps if we try to run gcc 3.4.3 built binaries on gcc 3.4.6 machine. Machines are not normally specific to a version of gcc. gcc 3.4.3 and gcc 3.4.6 are compatible. Note that the C library, glibc, is not part of gcc. > The stack trace we have 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 () > > We are not sure if there are any incompatibility issues between those two gcc version. I have attached patches on the target machine. This looks like something clobbered memory somewhere, and it was noticed after the program exited. If that is the problem, it is almost certainly not a gcc problem. You may get some help from MALLOC_CHECK_ (see the malloc man page) or from valgrind. Ian
