From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com,
jimb@redhat.com, fedor@doc.com
Subject: Re: RFA symtab: Fix for PR c++/1267 ("next" and shared libraries)
Date: Mon, 21 Jul 2003 18:22:00 -0000 [thread overview]
Message-ID: <3F1C2F6A.30607@redhat.com> (raw)
In-Reply-To: <20030721162750.GA6754@nevyn.them.org>
>
> No, really, I still think that the comment is wrong. The get_frame_id
> call triggers the prologue analyzer to analyze the NEXT frame. I.E.
> this_id is called with the NEXT frame, and THIS cache.
Nope. get_frame_id triggers the analysis of THIS frame's prologue (i.e.,
next_frame & this_cache).
> The call to frame_pc_unwind uses THIS frame and creates the PREV cache.
> It's one frame off on the stack. The frame it would be saving from
> prologue analysis is not the one we'd need to analyze for the
> get_frame_id call.
Nope. frame_pc_unwind would turn into frame_register_unwind (this,
PC_REGNUM) and that will also trigger the analysis of THIS frame's
prologue (i.e., next_frame & this_cache).
Andrew
next prev parent reply other threads:[~2003-07-21 18:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 18:18 Daniel Jacobowitz
2003-07-20 3:30 ` Adam Fedor
2003-07-21 7:11 ` Jim Blandy
2003-07-21 12:53 ` Daniel Jacobowitz
2003-07-24 19:59 ` Jim Blandy
2003-07-24 20:58 ` Daniel Jacobowitz
2003-07-24 21:34 ` Adam Fedor
2003-07-25 0:12 ` Jim Blandy
2003-07-25 6:07 ` Eli Zaretskii
2003-07-25 12:58 ` Daniel Jacobowitz
2003-07-28 2:38 ` Daniel Jacobowitz
2003-07-21 16:18 ` Andrew Cagney
2003-07-21 16:27 ` Daniel Jacobowitz
2003-07-21 18:22 ` Andrew Cagney [this message]
2003-07-21 21:23 ` Daniel Jacobowitz
2003-07-25 16:15 Michael Elizabeth Chastain
2003-07-25 16:20 ` Daniel Jacobowitz
2003-07-25 16:24 Michael Elizabeth Chastain
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=3F1C2F6A.30607@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=fedor@doc.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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