public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Frame handling
Date: Tue, 01 Jul 2003 12:45:00 -0000	[thread overview]
Message-ID: <20030701124535.GA9334@nevyn.them.org> (raw)
In-Reply-To: <00cd01c33f8d$b4e570e0$0a00a8c0@nkelseyhome>

On Mon, Jun 30, 2003 at 10:00:21PM -0700, Jafa wrote:

> Out of interest, what is the theory behind the frame id being made up of
> address + func?

The theory is that the frame ID is persistent.  It lives until the
frame goes out of scope (locals with watchpoints on them disappear,
frame-specific breakpoints, etc.).  Stack addr isn't enough, because of
frameless functions; but PC is too volatile.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-07-01 12:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01  5:00 Jafa
2003-07-01 12:45 ` Daniel Jacobowitz [this message]
2003-07-01 13:02 ` Andrew Cagney
2003-07-03  9:05   ` Paul N. Hilfinger
  -- strict thread matches above, loose matches on Subject: below --
2003-07-01  1:20 Jafa
2003-07-01  3:42 ` Daniel Jacobowitz
2003-07-01  4:18   ` Andrew Cagney
     [not found]   ` <redirect-6800274@silicondust.com>
2003-07-01  5:13     ` Jafa
2003-07-01 12:58       ` Andrew Cagney
2003-07-01 14:09         ` Daniel Jacobowitz
2003-07-01 14:57           ` Andrew Cagney
     [not found]           ` <redirect-6810110@silicondust.com>
2003-07-01 17:00             ` Jafa
     [not found]       ` <redirect-6810084@silicondust.com>
2003-07-01 16:14         ` Jafa
2003-07-01 17:59           ` Andrew Cagney
2003-04-08 18:35 Jafa
2003-04-14  3:43 ` Andrew Cagney

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=20030701124535.GA9334@nevyn.them.org \
    --to=drow@mvista.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).