Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>,
	Jason R Thorpe <thorpej@wasabisystems.com>,
	Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] x86-64 targeted gdb and corefiles
Date: Tue, 28 May 2002 19:30:00 -0000	[thread overview]
Message-ID: <3CF43AA0.6070205@cygnus.com> (raw)
In-Reply-To: <20020527184029.GA29774@branoic.them.org>

> 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)();
> };

While something like this is definitly needed, I think it is getting 
slightly beyond the bounds of what MichaelL needs to do - get core files 
working, using current mechanisms, for x86-64.

enjoy,
Andrew



  parent reply	other threads:[~2002-05-29  2:19 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
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 [this message]
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=3CF43AA0.6070205@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=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