Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] Fix SP register unwinding on alpha-tru64
Date: Fri, 30 May 2008 15:20:00 -0000	[thread overview]
Message-ID: <200805292132.m4TLW9TA009207@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080529205215.GG13826@adacore.com> from "Joel Brobecker" at May 29, 2008 01:52:15 PM

Joel Brobecker wrote:

> Index: alpha-tdep.c
> ===================================================================
> --- alpha-tdep.c	(revision 131678)
> +++ alpha-tdep.c	(working copy)
> @@ -1175,6 +1175,10 @@ alpha_heuristic_frame_prev_register (str
>    struct alpha_heuristic_unwind_cache *info
>      = alpha_heuristic_frame_unwind_cache (this_frame, this_prologue_cache, 0);
>  
> +  /* The stack pointer of the previous frame is this frame's vfp.  */
> +  if (regnum == ALPHA_SP_REGNUM)
> +    return frame_unwind_got_constant (this_frame, regnum, info->vfp);
> +
>    /* The PC of the previous frame is stored in the link register of
>       the current frame.  Frob regnum so that we pull the value from
>       the correct place.  */

Hmm, in alpha-mdebug-tdep.c this is now implemented as:

  /* The stack pointer of the previous frame is computed by popping
     the current stack frame.  */
  if (!trad_frame_addr_p (info->saved_regs, ALPHA_SP_REGNUM))
   trad_frame_set_value (info->saved_regs, ALPHA_SP_REGNUM, vfp);

at the end of alpha_mdebug_frame_unwind_cache ...

Should the two files use the same method here?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-05-29 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 15:13 Joel Brobecker
2008-05-30 15:20 ` Ulrich Weigand [this message]
2008-05-31  6:46   ` Joel Brobecker

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=200805292132.m4TLW9TA009207@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.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