Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb-patches@sources.redhat.com
Subject: [rfa] PPC/Linux native - don't use greg_t
Date: Thu, 05 Jul 2001 14:40:00 -0000	[thread overview]
Message-ID: <20010705144015.A26893@nevyn.them.org> (raw)

At least my installed systems don't actually define greg_t in headers any
more, unless you include <linux/elfcore.h> explicitly - which you can't,
since it conflicts with <sys/procfs.h>.  I'm not convinced that that's
right, but since we are defining gdb_gregset_t to be an elf_gregset_t
already, using elf_greg_t makes sense to me.  OK to commit?

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

2001-07-05  Daniel Jacobowitz  <drow@mvista.com>

	* ppc-linux-nat.c (supply_gregset): Use elf_greg_t instead
	of greg_t.
	(fill_gregset): Likewise.

--- ppc-linux-nat.c.orig	Thu Jul  5 14:34:58 2001
+++ ppc-linux-nat.c	Thu Jul  5 14:34:29 2001
@@ -63,7 +63,7 @@
 supply_gregset (gdb_gregset_t *gregsetp)
 {
   int regi;
-  register greg_t *regp = (greg_t *) gregsetp;
+  register elf_greg_t *regp = (elf_greg_t *) gregsetp;
 
   for (regi = 0; regi < 32; regi++)
     supply_register (regi, (char *) (regp + regi));
@@ -76,7 +76,7 @@
 fill_gregset (gdb_gregset_t *gregsetp, int regno)
 {
   int regi;
-  greg_t *regp = (greg_t *) gregsetp;
+  elf_greg_t *regp = (elf_greg_t *) gregsetp;
 
 #define COPY_REG(_idx_,_regi_) \
   if ((regno == -1) || regno == _regi_) \


             reply	other threads:[~2001-07-05 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 14:40 Daniel Jacobowitz [this message]
2001-07-05 16:16 ` Kevin Buettner
2001-07-05 16:22   ` 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=20010705144015.A26893@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --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