From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -stack-info-frame/-stack-list-frames
Date: Wed, 23 Apr 2008 06:03:00 -0000 [thread overview]
Message-ID: <18446.49934.972945.419064@kahikatea.snap.net.nz> (raw)
In-Reply-To: <fumei3$vro$1@ger.gmane.org>
> > Here's a patch to add the frame address to the output of -stack-info-frame
> > and -stack-list-frames and async output when execution stops. It also
> > outputs the source language for -stack-info-frame, these change making it
> > more like "info frame":
>
> Could you first clarify that is the purpose of said fields -- especially
> frame address?
The frame address is probably of more interest than the pc address, at least
for frames other than the current one. If the call stack includes the frame
address for each frame and the watch window gives the variable's address
then it is possible to infer to which frame that variable belongs. In any
case, the extra field comes at almost no cost and a frontend can choose to
ignore it.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-23 5:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 5:33 Nick Roberts
2008-04-23 5:48 ` Vladimir Prus
2008-04-23 6:03 ` Nick Roberts [this message]
2008-04-23 6:16 ` Vladimir Prus
2008-04-23 9:50 ` Nick Roberts
2008-04-23 10:32 ` Vladimir Prus
2008-04-23 13:23 ` Nick Roberts
2008-04-23 13:44 ` Daniel Jacobowitz
2008-04-23 23:04 ` Nick Roberts
2008-04-23 23:27 ` Daniel Jacobowitz
2008-04-24 0:40 ` Bob Rossi
2008-04-24 1:45 ` Nick Roberts
2008-04-24 1:31 ` Nick Roberts
2008-04-24 1:48 ` Nick Roberts
2008-04-24 10:24 ` Daniel Jacobowitz
2008-04-25 1:48 ` Nick Roberts
2008-04-25 2:03 ` Daniel Jacobowitz
2008-04-25 11:41 ` Nick Roberts
2008-04-23 13:53 ` Vladimir Prus
2008-04-23 23:23 ` Nick Roberts
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=18446.49934.972945.419064@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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