Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: gdb-patches@sourceware.org
Subject: patch: signal trampoline frame cache corruption (repost?)
Date: Tue, 31 Oct 2006 19:41:00 -0000	[thread overview]
Message-ID: <1162323227.3428.9.camel@dufur.beaverton.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

This might be a repost.  

Attached is a patch to fix some signal trampoline frame cache corruption
that occurs on machines that have no FPU registers.  The corruption was
reported when running gdb 6.4 on a PowerPC 440.  If a backtrace command
was run after hitting a signal trampoline frame, the frame cache would
become corrupted and GDB would SIGSEGV.

I have checked the cvs head sources, and the code has moved, but has not
been fixed.  So I updated the patch to apply to cvs head.

Ok to commit?  (This is almost an obvious fix, isn't it?)



[-- Attachment #2: fix-sigtramp-cache.patch --]
[-- Type: text/x-patch, Size: 1049 bytes --]

---
 gdb/ppc-linux-tdep.c |   18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

--- gdb-6.4.orig/gdb/ppc-linux-tdep.c
+++ gdb-6.4/gdb/ppc-linux-tdep.c
@@ -967,14 +967,16 @@ ppc_linux_sigtramp_cache (struct frame_i
   trad_frame_set_reg_addr (this_cache, tdep->ppc_cr_regnum,
 			   gpregs + 38 * tdep->wordsize);
 
-  /* Floating point registers.  */
-  for (i = 0; i < 32; i++)
-    {
-      int regnum = i + FP0_REGNUM;
-      trad_frame_set_reg_addr (this_cache, regnum, fpregs + i * tdep->wordsize);
-    }
-  trad_frame_set_reg_addr (this_cache, tdep->ppc_fpscr_regnum,
-			   fpregs + 32 * tdep->wordsize);
+  if (ppc_floating_point_unit_p(gdbarch)) {
+	  /* Floating point registers.  */
+	  for (i = 0; i < 32; i++)
+	  {
+		  int regnum = i + FP0_REGNUM;
+		  trad_frame_set_reg_addr (this_cache, regnum, fpregs + i * tdep->wordsize);
+	  }
+	  trad_frame_set_reg_addr (this_cache, tdep->ppc_fpscr_regnum,
+			  fpregs + 32 * tdep->wordsize);
+  }
   trad_frame_set_id (this_cache, frame_id_build (base, func));
 }
 

             reply	other threads:[~2006-10-31 19:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 19:41 PAUL GILLIAM [this message]
2006-10-31 23:28 ` Mark Kettenis
2006-11-03 17:58   ` PAUL GILLIAM
2006-11-10 21:22     ` Daniel Jacobowitz
2006-11-13 17:42       ` [commit] signal trampoline frame cache corruption PAUL GILLIAM
2006-11-13 17:46         ` Daniel Jacobowitz
2006-11-13 18:57           ` PAUL GILLIAM
2006-11-13 19:05             ` Daniel Jacobowitz
2006-11-14  1:50               ` PAUL GILLIAM

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=1162323227.3428.9.camel@dufur.beaverton.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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