From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/alpha-osf] another next frame confusion in signal unwinder?
Date: Sun, 12 Dec 2004 16:27:00 -0000 [thread overview]
Message-ID: <41BC67C0.6080106@gnu.org> (raw)
In-Reply-To: <20041201235125.GL1001@adacore.com>
Joel Brobecker wrote:
> It looks to me that we already have the next frame, so computing
> the next frame of that frame in alpha_osf1_sigcontext_addr() is
> making us using the wrong frame when getting the base address for
> the signal context area. So I changed this function to:
>
> static CORE_ADDR
> alpha_osf1_sigcontext_addr (struct frame_info *next_frame)
> {
> return (read_memory_integer (get_frame_base (next_frame), 8));
> }
>
> This fixes the problem above, and I obtain the expected callstack.
>
> 2004-12-01 Joel Brobecker <brobecker@gnat.com>
>
> * alpha-osf1-tdep.c (alpha_osf1_sigcontext_addr): Change
> parameter name to make it clear that we already have a next
> frame. Return the sigcontext from that next frame instead
> of the frame following it.
> Fixes [DB30-017].
>
> Tested on alpha-tru64 5.1a. No regression.
>
> OK to apply?
>
>
> ------------------------------------------------------------------------
>
> Index: alpha-osf1-tdep.c
> ===================================================================
> RCS file: /nile.c/cvs/Dev/gdb/gdb-6.3/gdb/alpha-osf1-tdep.c,v
> retrieving revision 1.3
> diff -u -p -r1.3 alpha-osf1-tdep.c
> --- alpha-osf1-tdep.c 21 Oct 2004 00:08:34 -0000 1.3
> +++ alpha-osf1-tdep.c 1 Dec 2004 17:54:46 -0000
> @@ -35,14 +35,9 @@ alpha_osf1_pc_in_sigtramp (CORE_ADDR pc,
> }
>
> static CORE_ADDR
> -alpha_osf1_sigcontext_addr (struct frame_info *frame)
> +alpha_osf1_sigcontext_addr (struct frame_info *next_frame)
> {
> - struct frame_info *next_frame = get_next_frame (frame);
> -
> - if (next_frame != NULL)
> - return (read_memory_integer (get_frame_base (next_frame), 8));
> - else
> - return (read_memory_integer (get_frame_base (frame), 8));
> + return (read_memory_integer (get_frame_base (next_frame), 8));
(I need to deprecate get frame base). Can you just tweak this to return
get_frame_id().stack_addr before committing.
thanks,
Andrew
> }
>
> static void
next prev parent reply other threads:[~2004-12-12 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 23:51 Joel Brobecker
2004-12-12 16:27 ` Andrew Cagney [this message]
2004-12-13 8:43 ` 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=41BC67C0.6080106@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@adacore.com \
--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