Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: frame cache
Date: Tue, 24 Jul 2007 17:36:00 -0000	[thread overview]
Message-ID: <20070724171711.GB15843@caradoc.them.org> (raw)
In-Reply-To: <46A63209.4010405@eagercon.com>

On Tue, Jul 24, 2007 at 10:08:25AM -0700, Michael Eager wrote:
> And one more question:
> 
> 3)  In <target>_skip_prologue(), an dummy <target>_frame_cache is
>     created to be passed to <target>_analyze_prologue().  This
>     dummy cache entry is discarded.   Why not retain this info?

I think the answers to your other two questions should clarify this.
We don't have anywhere to keep it, and the information is not quite
the same because it depends how far into the function we're allowed to
analyze (the PC "limit").  Also, many targets don't do it this way.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-07-24 17:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 17:08 Michael Eager
2007-07-24 17:14 ` Michael Eager
2007-07-24 17:36   ` Daniel Jacobowitz [this message]
2007-07-24 18:19     ` Michael Eager
2007-07-24 18:34       ` Daniel Jacobowitz
2007-07-24 18:34       ` Mark Kettenis
2007-07-24 17:17 ` Daniel Jacobowitz
2007-07-24 18:10   ` Michael Eager
2007-07-24 18:22     ` Daniel Jacobowitz
2007-07-24 18:45       ` Michael Eager
2007-07-24 18:45     ` Mark Kettenis
2007-07-24 19:08       ` Michael Eager
2007-07-25  2:18         ` Paul Koning
2007-07-27  9:18         ` Wenbo Yang
2007-07-30 22:01           ` Michael Eager
2007-07-30 23:07             ` Mark Kettenis
2007-07-31  3:51             ` Wenbo Yang

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=20070724171711.GB15843@caradoc.them.org \
    --to=drow@false.org \
    --cc=eager@eagercon.com \
    --cc=gdb@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