Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Some regset-related cleanup for i386bsd-nat.c
Date: Wed, 09 Jun 2004 16:20:00 -0000	[thread overview]
Message-ID: <40C738A7.9040900@gnu.org> (raw)
In-Reply-To: <mtuu0xlu65w.fsf@contents-vnder-pressvre.mit.edu>

> Mark Kettenis <kettenis@chello.nl> writes:
> 
> 
>>> 	* i386bsd-nat.c: Don't include "gregset.h".
>>> 	(supply_gregset, fill_gregset): Make static.
>>> 	(supply_fpregset, fill_fpregset): Remove.
> 
> 
> I just noticed this in one of my builds. I'm attempting to modernize
> and prepare my NetBSD thread support code for integration, and that
> code uses the {supply,fill}_{regset,fpregset} functions to implement
> the thread-specific fetch_registers and store_registers, based on
> register context passed back from the pthread debugging library (It
> was quite a boon when I ported it forward from 5.0 to 5.3 and got
> these functions to use). If these are removed, is there a good way for
> an architecture-neutral bit of code like nbsd-thread.c to go back and
> forth between GDB's register storage and native register storage?

Have a look at regsets.[hc], the method:
   set_gdbarch_regset_from_core_section (gdbarch, 
ppc_linux_regset_from_core_section);
they set the general direction for where GDB is going.

Andrew



      parent reply	other threads:[~2004-06-09 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 10:01 Mark Kettenis
2004-06-08 20:49 ` Nathan J. Williams
2004-06-08 23:38   ` Mark Kettenis
2004-06-09 16:20   ` Andrew Cagney [this message]

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=40C738A7.9040900@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=nathanw@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