From: Jon Zhou <Jon.Zhou@jdsu.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: support biarch gcore?
Date: Mon, 05 Jul 2010 04:54:00 -0000 [thread overview]
Message-ID: <4A6A2125329CFD4D8CC40C9E8ABCAB9F24987E52BB@MILEXCH2.ds.jdsu.net> (raw)
In-Reply-To: <4A25DE879BC24E8DAEAEBD722E363025@igor>
Hi there
Regarding this case, does the current release solve it ? I just tried the patch but looks it doesn't work
Thanks
jon
http://sourceware.org/ml/gdb/2009-03/msg00010.html
Re: Problem viewing gcore of 32 bit binary on 64 bit SLES 10.1, gdb 6.6
From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
To: Shane G <pachoo at gmail dot com>
Cc: gdb at sourceware dot org
Date: Tue, 3 Mar 2009 00:10:28 +0100
Subject: Re: Problem viewing gcore of 32 bit binary on 64 bit SLES 10.1, gdb 6.6
References: <985ad4e70903021500u594a4c4w30eff9ae287f5e8d@mail.gmail.com>
--------------------------------------------------------------------------------
On Tue, 03 Mar 2009 00:00:57 +0100, Shane G wrote:
> I'm unable to view any usable information from a gcore that I've run
> against a 32 bit binary running on a 64 bit version of SLES 10.1.
from your description IMO the core file is primarily generated wrong by gcore.
If you somewhere get a correct 32bit core file expecting gdb-x86_64 probably
reads it fine on your system.
> This GDB was configured as "x86_64-suse-linux"...
At least in
http://download.opensuse.org/repositories/home:/dgollub/openSUSE_Factory/src/gdb-6.8-14.80.src.rpm
I see no gcore biarch patch and FSF GDB does not support biarch gcore (in this
case i386-on-x86_64). You may port there the patch:
http://cvs.fedora.redhat.com/viewvc/rpms/gdb/devel/gdb-6.5-gcore-i386-on-amd64.patch?revision=1.6
Regards,
Jan
next prev parent reply other threads:[~2010-07-05 4:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 10:48 Examining copied stack contents Martin Schröder
2010-07-05 4:54 ` Jon Zhou [this message]
2010-07-05 7:12 ` support biarch gcore? Jan Kratochvil
2010-07-05 11:55 ` Mark Kettenis
2010-07-06 20:48 ` Ulrich Weigand
2010-07-06 21:29 ` Mark Kettenis
2010-07-07 12:30 ` Ulrich Weigand
2010-07-08 2:35 ` Jon Zhou
2010-07-08 11:17 ` Ulrich Weigand
2010-07-08 4:47 ` H.J. Lu
2010-07-08 5:05 ` H.J. Lu
2010-07-08 11:15 ` Ulrich Weigand
2010-07-08 13:52 ` H.J. Lu
2010-07-21 22:45 ` Joseph S. Myers
2010-07-05 18:50 ` Examining copied stack contents Petr Hluzín
2010-07-05 20:18 ` Martin Schröder
2010-07-05 20:27 ` Joel Brobecker
2010-07-07 17:29 ` Martin Schröder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A6A2125329CFD4D8CC40C9E8ABCAB9F24987E52BB@MILEXCH2.ds.jdsu.net \
--to=jon.zhou@jdsu.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).