Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Backtrace prints wrong argument value
Date: Mon, 17 Sep 2007 17:15:00 -0000	[thread overview]
Message-ID: <1190049306.4651.42.camel@localhost> (raw)
In-Reply-To: <20070917140416.GA15635@caradoc.them.org>

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

Daniel,

This version appears to fix the tabs, spaces and identation.

-- 
Luis Machado
IBM Linux Technology Center
e-mail: luisgpm@linux.vnet.ibm.com

[-- Attachment #2: call-clobbered-registers.diff --]
[-- Type: text/x-patch, Size: 3204 bytes --]

2007-09-17  Luis Machado  <luisgpm@br.ibm.com>

    * rs6000-tdep.c (ppc_dwarf2_frame_init_reg): New function.
      (rs6000_gdbarch_init): Install ppc_dwarf2_frame_init_reg as 
      default dwarf2_frame_set_init_reg function.

Index: gdb/rs6000-tdep.c
===================================================================
--- gdb.orig/rs6000-tdep.c	2007-09-17 06:41:23.000000000 -0700
+++ gdb/rs6000-tdep.c	2007-09-17 10:05:27.000000000 -0700
@@ -3468,6 +3468,68 @@
   return &rs6000_frame_base;
 }
 
+/* DWARF-2 frame support.  Used to handle the detection of
+  clobbered registers during function calls.  */
+
+static void
+ppc_dwarf2_frame_init_reg (struct gdbarch *gdbarch, int regnum,
+			    struct dwarf2_frame_state_reg *reg,
+			    struct frame_info *next_frame)
+{
+  struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
+
+  /* PPC32 and PPC64 ABI's are the same regarding volatile and
+     non-volatile registers.  We will use the same code for both.  */
+
+  /* Call-saved GP registers.  */
+  if ((regnum >= tdep->ppc_gp0_regnum + 14
+      && regnum <= tdep->ppc_gp0_regnum + 31)
+      || (regnum == tdep->ppc_gp0_regnum + 1))
+    reg->how = DWARF2_FRAME_REG_SAME_VALUE;
+
+  /* Call-clobbered GP registers.  */
+  if ((regnum >= tdep->ppc_gp0_regnum + 3
+      && regnum <= tdep->ppc_gp0_regnum + 12)
+      || (regnum == tdep->ppc_gp0_regnum))
+    reg->how = DWARF2_FRAME_REG_UNDEFINED;
+
+  /* Deal with FP registers, if supported.  */
+  if (tdep->ppc_fp0_regnum >= 0)
+    {
+      /* Call-saved FP registers.  */
+      if ((regnum >= tdep->ppc_fp0_regnum + 14
+	  && regnum <= tdep->ppc_fp0_regnum + 31))
+	reg->how = DWARF2_FRAME_REG_SAME_VALUE;
+
+      /* Call-clobbered FP registers.  */
+      if ((regnum >= tdep->ppc_fp0_regnum
+	  && regnum <= tdep->ppc_fp0_regnum + 13))
+	reg->how = DWARF2_FRAME_REG_UNDEFINED;
+    }
+
+  /* Deal with ALTIVEC registers, if supported.  */
+  if (tdep->ppc_vr0_regnum > 0 && tdep->ppc_vrsave_regnum > 0)
+    {
+      /* Call-saved Altivec registers.  */
+      if ((regnum >= tdep->ppc_vr0_regnum + 20
+	  && regnum <= tdep->ppc_vr0_regnum + 31)
+	  || regnum == tdep->ppc_vrsave_regnum)
+	reg->how = DWARF2_FRAME_REG_SAME_VALUE;
+
+      /* Call-clobbered Altivec registers.  */
+      if ((regnum >= tdep->ppc_vr0_regnum
+	  && regnum <= tdep->ppc_vr0_regnum + 19))
+	reg->how = DWARF2_FRAME_REG_UNDEFINED;
+    }
+
+  /* Handle PC register and Stack Pointer correctly.  */
+  if (regnum == gdbarch_pc_regnum (current_gdbarch))
+    reg->how = DWARF2_FRAME_REG_RA;
+  else if (regnum == gdbarch_sp_regnum (current_gdbarch))
+    reg->how = DWARF2_FRAME_REG_CFA;
+}
+
+
 /* Initialize the current architecture based on INFO.  If possible, re-use an
    architecture from ARCHES, which is a list of architectures already created
    during this debugging session.
@@ -3774,6 +3836,9 @@
   frame_unwind_append_sniffer (gdbarch, dwarf2_frame_sniffer);
   dwarf2_frame_set_adjust_regnum (gdbarch, rs6000_adjust_frame_regnum);
 
+  /* Frame handling.  */
+  dwarf2_frame_set_init_reg (gdbarch, ppc_dwarf2_frame_init_reg);
+
   /* Hook in ABI-specific overrides, if they have been registered.  */
   gdbarch_init_osabi (info, gdbarch);
 

  parent reply	other threads:[~2007-09-17 17:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 19:13 Luis Machado
2007-04-25 19:25 ` Daniel Jacobowitz
2007-04-25 22:28   ` Luis Machado
2007-04-30 13:31     ` Luis Machado
2007-05-16  5:34   ` Luis Machado
2007-05-16 14:43     ` Daniel Jacobowitz
2007-05-16 15:20       ` Luis Machado
2007-05-16 15:23         ` Daniel Jacobowitz
2007-09-13 14:47       ` Luis Machado
2007-09-16 19:45         ` Daniel Jacobowitz
2007-09-17 13:05           ` Luis Machado
2007-09-17 13:15             ` Daniel Jacobowitz
2007-09-17 13:30               ` Luis Machado
2007-09-17 13:37                 ` Daniel Jacobowitz
2007-09-17 13:46                   ` Luis Machado
2007-09-17 14:00                   ` Luis Machado
2007-09-17 14:04                     ` Daniel Jacobowitz
2007-09-17 16:02                       ` Luis Machado
2007-09-17 17:15                       ` Luis Machado [this message]
2007-09-17 17:18                         ` Daniel Jacobowitz
2007-09-17 17:34                           ` Luis Machado
2007-09-17 17:48                             ` Daniel Jacobowitz
2007-10-03 14:58                               ` Luis Machado
2007-10-21 21:41                           ` Luis Machado
2007-10-22  0:03                             ` Joel Brobecker
2007-10-22  1:20                               ` Daniel Jacobowitz
2007-10-22  4:11                                 ` Joel Brobecker
2007-10-24 20:50                                   ` Daniel Jacobowitz
2007-10-24 20:59                                     ` Joel Brobecker
2007-10-24 21:01                                       ` Daniel Jacobowitz
2007-10-24 22:23                                     ` Pedro Alves
2007-10-24 22:38                                       ` Pedro Alves

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=1190049306.4651.42.camel@localhost \
    --to=luisgpm@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --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