This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb 7.2: problem reading core generated by executable compiled by gcc-4.1.2/glibc-2.5-24
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Pawel K <mafeusek at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 13 Sep 2010 10:41:27 +0200
- Subject: Re: gdb 7.2: problem reading core generated by executable compiled by gcc-4.1.2/glibc-2.5-24
- References: <AANLkTi=Pts8rCAMOU5xN96nizVo2p6hCHn=gPaQVVcx-@mail.gmail.com>
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