Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/ppc/branch too] Fix PowerPC/Linux cores
Date: Thu, 02 Aug 2001 12:08:00 -0000	[thread overview]
Message-ID: <20010802120808.A3911@nevyn.them.org> (raw)
In-Reply-To: <1010731004934.ZM5803@ocotillo.lan>

On Mon, Jul 30, 2001 at 05:49:34PM -0700, Kevin Buettner wrote:
> I have no objection to it going on the branch; but I'd prefer to not
> see it go in on the trunk.  OTOH, I'd have no objection to a patch
> which updates core-regset.c to use gdb_gregset_t / gdb_fpregset_t
> being applied to either the 5.1 release branch or the trunk.  I'm
> not quibbling about correctness, but I'd prefer to see it done the
> "right" way on the trunk.  That could mean using gdb_*regset_t in
> core-regset.c or it could mean using your upcoming cross platform
> corefile support or perhaps some combination.

Fixing it "right" will be cross corefile support, but changing
core-regset is correct for now.  If no one objects I'm going to check
in the below patch tomorrow, branch and trunk (when is the branch
release point supposed to be?  Isn't it coming up on us now?).

I tested the patch on powerpc-linux, and it works exactly as expected.

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

2001-08-02  Daniel Jacobowitz  <drow@mvista.com>

	* core-regset.c (fetch_core_registers):  Remove HAVE_GREGSET_T
	and HAVE_FPREGSET_T checks.  Use gdb_gregset_t and
	gdb_fpregset_t.

--- gdb-5.0.cvs20010729/gdb/core-regset.c.orig	Thu Aug  2 11:26:38 2001
+++ gdb-5.0.cvs20010729/gdb/core-regset.c	Thu Aug  2 11:27:05 2001
@@ -84,9 +84,8 @@
 fetch_core_registers (char *core_reg_sect, unsigned core_reg_size, int which,
 		      CORE_ADDR reg_addr)
 {
-#if defined (HAVE_GREGSET_T) && defined (HAVE_FPREGSET_T)
-  gregset_t gregset;
-  fpregset_t fpregset;
+  gdb_gregset_t gregset;
+  gdb_fpregset_t fpregset;
 
   if (which == 0)
     {
@@ -113,7 +112,6 @@
 	    supply_fpregset (&fpregset);
 	}
     }
-#endif /* defined(HAVE_GREGSET_T) && defined (HAVE_FPREGSET_T) */
 }
 \f
 


  parent reply	other threads:[~2001-08-02 12:08 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
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 [this message]
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=20010802120808.A3911@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@cygnus.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