From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] x86-64 targeted gdb and corefiles
Date: Mon, 27 May 2002 11:27:00 -0000 [thread overview]
Message-ID: <20020527111157.A22765@dr-evil.shagadelic.org> (raw)
In-Reply-To: <3CF24B2A.3070305@suse.cz>; from mludvig@suse.cz on Mon, May 27, 2002 at 05:05:14PM +0200
On Mon, May 27, 2002 at 05:05:14PM +0200, Michal Ludvig wrote:
> Hi all,
> this patch allows reading of coredumps on non-native gdb configured for
> x86-64 target. It works pretty well in this form, but I had to modify
> gregset.h, what is unwise. I know I have to move the modifications
> somewhere else, but ... where? Can someone give me an advice, please?
Take a look at e.g. mipsnbsd-nat.c and mipsnbsd-tdep.c (I'm slowly
making all NetBSD configurations fully cross-debug'able, and MIPS
and SH are good examples of my strategy).
As far as I'm concerned, it's simply not appropriate to be using generic
"regset" routines, because the names of those routines inherently make
them impossible to use for cross-debugging, especially in a truly multi-arch
environment (or even one as simple as "32-bit code running on x86-64").
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-05-27 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 8:58 Michal Ludvig
2002-05-27 11:27 ` Jason R Thorpe [this message]
2002-05-27 12:01 ` Daniel Jacobowitz
2002-05-27 12:24 ` Jason R Thorpe
2002-05-28 3:50 ` Daniel Jacobowitz
2002-05-28 8:33 ` Jason R Thorpe
2002-05-28 19:30 ` Andrew Cagney
2002-05-27 15:00 Mark Kettenis
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=20020527111157.A22765@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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