From: Daniel Jacobowitz <drow@mvista.com>
To: Jason R Thorpe <thorpej@wasabisystems.com>,
Michal Ludvig <mludvig@suse.cz>,
GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] x86-64 targeted gdb and corefiles
Date: Mon, 27 May 2002 12:01:00 -0000 [thread overview]
Message-ID: <20020527184029.GA29774@branoic.them.org> (raw)
In-Reply-To: <20020527111157.A22765@dr-evil.shagadelic.org>
On Mon, May 27, 2002 at 11:11:57AM -0700, Jason R Thorpe wrote:
> 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").
Seconded; perhaps with all the attention cross cores have been getting
lately it's time for a better framework for this? I was thinking
something like:
struct regset_handler {
enum type regset_kind; /* general, FP, extended */
int size;
void (*supply)();
void (*fetch)();
};
See gdbserver's regset handling for a more concrete example of this.
This could be used to kill all the duplicate copies of core-regset.c
that have made their way into i386 and powerpc tdep files.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-27 18:41 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
2002-05-27 12:01 ` Daniel Jacobowitz [this message]
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=20020527184029.GA29774@branoic.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
--cc=thorpej@wasabisystems.com \
/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