Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Tue, 28 May 2002 03:50:00 -0000	[thread overview]
Message-ID: <20020528081103.GA5367@branoic.them.org> (raw)
In-Reply-To: <20020527120111.B22765@dr-evil.shagadelic.org>

On Mon, May 27, 2002 at 12:01:11PM -0700, Jason R Thorpe wrote:
> On Mon, May 27, 2002 at 02:40:29PM -0400, Daniel Jacobowitz wrote:
> 
>  > 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.
> 
> Yah, probably not a bad idea.  My only concern would be how do you
> register and look up these regset handlers.  They need to be tied
> to the OS ABI somehow.

You just said the "how" yourself :)

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-05-28  8:11 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 [this message]
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=20020528081103.GA5367@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