gdb 7.2: problem reading core generated by executable compiled by gcc-4.1.2/glibc-2.5-24

gdb 7.2: problem reading core generated by executable compiled by gcc-4.1.2/glibc-2.5-24

[Pawel K]

Hallo Group Members.

I just compiled and installed gdb 7.2 on my Redhat 5.x system just to
get python support.

I need to debug a core that was produced by (multithreaded) executable
 compiled and run on this system.
Unfortunatelly on gdb 7.2 I get following error:
(gdb) core core.5595
"/var/tmp/core.5595" is not a core dump: File format not recognized

when I load the core into gdb.6.5 its format is recognized and
everything works fine.

Is it expected behavour, did I misconfigured something or is it a bug?

best regards,
Pawel

Re: gdb 7.2: problem reading core generated by executable compiled by gcc-4.1.2/glibc-2.5-24

[Jan Kratochvil]

On Mon, 13 Sep 2010 10:28:34 +0200, Pawel K wrote:
> I just compiled and installed gdb 7.2 on my Redhat 5.x system just to
> get python support.

offtopic part here but:
If you mean Red Hat Enterprise Linux (AKA RHEL) 5.x then you can use
from RHEL 5.5 or CentOS 5.5:
rpmbuild --rebuild --with python gdb-7.0.1-23.el5.src.rpm
`--with python' would be default (but the binary rpms do not have it).
Such binary will not be unsupported.


> I need to debug a core that was produced by (multithreaded) executable
>  compiled and run on this system.
> Unfortunatelly on gdb 7.2 I get following error:
> (gdb) core core.5595
> "/var/tmp/core.5595" is not a core dump: File format not recognized

You should compare what `file /var/tmp/core.5595' thinks about it together
with what prints just `gdb' when you run it:
This GDB was configured as "[...?]".


Regards,
Jan

Re: gdb 7.2: problem reading core generated by executable compiled by gcc-4.1.2/glibc-2.5-24

[Pawel K]

Hallo Jan

prompt# file ./binary.debug
./binary.debug: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs),
for GNU/Linux 2.6.9, not stripped

prompt# file ./core.15070
./core.15070: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV),
SVR4-style, from 'binary'


> If you mean Red Hat Enterprise Linux (AKA RHEL) 5.x then you can use
> from RHEL 5.5 or CentOS 5.5:
> rpmbuild --rebuild --with python gdb-7.0.1-23.el5.src.rpm
> `--with python' would be default (but the binary rpms do not have it).
> Such binary will not be unsupported.

unfortunatelly it didn't help:

prompt# gdb --annotate=3 ./binary.debug
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-redhat-linux".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from binary.debug...done.
(gdb) core core.15070
core.15070 is not a core dump: File format not recognized
(gdb)


> You should compare what `file /var/tmp/core.5595' thinks about it together
> with what prints just `gdb' when you run it:
> This GDB was configured as "[...?]".

by the way, gdb 7.2 compiled and installed from tar ball printed:
This GDB was configured as "i686-pc-linux-gnu".

where else can the problem be?

best regards,
Pawel