Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/ppc/branch too] Fix PowerPC/Linux cores
Date: Mon, 30 Jul 2001 15:44:00 -0000	[thread overview]
Message-ID: <1010730224404.ZM5571@ocotillo.lan> (raw)
In-Reply-To: <20010730142328.A6323@nevyn.them.org>

On Jul 30,  2:23pm, Daniel Jacobowitz wrote:

> I figure it would be nice if core files for Linux/PPC worked on the branch. 

It would be nice.  It even used to work.  :-(

> Linux/PPC doesn't have gregset_t or fpregset_t in its headers, so the body
> of fetch_core_registers in core-regset.c gets #if'd out by autoconf.  Cores
> load but are absolutely useless.  I have the feeling those #if's ought to be
> outside the function rather than inside...

You may be right.  The other alternative that occurs to me is to put
a #else branch in with a call to internal_error().  (It's a choice
between not linking vs. not running and it's not clear which way the
tradeoff should go.  Personally, when I'm doing a new baseport, I'd
rather have it link with the understanding that the functionality may
be limited...)

> but in any case, for now, this
> patch fixes it the same way most other Linux targets do.  I'll get back to
> my rework of core support in the next few weeks now that we've branched.
> 
> OK to commit, trunk and branch?

I think I'd like to explore some alternatives first.  The only
real difference that I see between the version of fetch_core_registers()
that you want to add to ppc-linux-nat.c and the one in core-regset.c is
that the former uses elf_{g,fp}regset_t whereas the latter uses
{g,fp}regset_t, right?

If that's the case, couldn't we simply make the core-regset.c version
use gdb_gregset_t and gdb_fpgregset_t?  That seems cleaner to me than
propagating nearly identical copies of fetch_core_registers() to the
various *-nat.c files.  (I see that mips-linux-tdep.c and
m68klinux-nat.c have taken the approach that you're suggesting;
i386-linux-nat.c has a good excuse for having its own version since
the format that it needs to support can't be handled by the generic
code.)


  reply	other threads:[~2001-07-30 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 14:23 Daniel Jacobowitz
2001-07-30 15:44 ` Kevin Buettner [this message]
2001-07-30 15:54   ` Daniel Jacobowitz
2001-07-30 17:50     ` Kevin Buettner
2001-07-30 17:57       ` Daniel Jacobowitz
2001-07-31  8:50         ` Andrew Cagney
2001-08-02 12:08       ` Daniel Jacobowitz
2001-08-02 12:48         ` Kevin Buettner
2001-08-03  8:39           ` Andrew Cagney
2001-08-03 14:36             ` Daniel Jacobowitz

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=1010730224404.ZM5571@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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