From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, Jim Ingham <jingham@apple.com>,
gdb@sources.redhat.com
Subject: Re: -var-update and address changes
Date: Sun, 16 Apr 2006 15:52:00 -0000 [thread overview]
Message-ID: <17474.11462.876311.964323@farnswood.snap.net.nz> (raw)
In-Reply-To: <20060414131549.GC12955@nevyn.them.org>
> > Can somebody suggest the right fix? So far, I think that the simplest
> > approach is to make gdb print stack address of current frame, like is done
> > on the Apple branch:
> >
> > 553^done,stack=[frame=
> > {level="0",addr="0x00003db0",fp="0xbffff2c0",......
> >
> > That way, frontend can deal with the issue of frame stacks themself, and
> > -var-update will be only used when single-stepping inside a given frame.
> > Will patches to implement this be welcome?
>
> I guess. It seems reasonable.
ISTR that Totalview displays the fp address of each frame in the call stack.
This seems natural and I wonder why "info stack" chooses to display the pc
addresses.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2006-04-16 11:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 16:02 Vladimir Prus
2006-04-12 18:25 ` Jim Ingham
2006-04-13 9:25 ` Vladimir Prus
2006-04-13 17:31 ` Jim Ingham
2006-04-14 13:25 ` Daniel Jacobowitz
2006-04-14 20:03 ` Jim Ingham
2006-04-14 20:09 ` Daniel Jacobowitz
2006-04-14 20:27 ` Jim Ingham
2006-04-14 21:37 ` Daniel Jacobowitz
2006-04-17 6:18 ` Vladimir Prus
2006-04-17 9:02 ` Mark Kettenis
2006-04-17 10:54 ` Vladimir Prus
2006-05-02 12:50 ` Vladimir Prus
2006-05-02 13:14 ` Nick Roberts
2006-05-02 13:41 ` Vladimir Prus
2006-05-02 17:23 ` Jim Ingham
2006-05-03 6:03 ` Vladimir Prus
[not found] ` <20060504145046.GA32605@nevyn.them.org>
2006-05-04 15:12 ` Vladimir Prus
2006-05-04 15:13 ` Daniel Jacobowitz
2006-05-05 6:25 ` Vladimir Prus
2006-05-05 15:02 ` Daniel Jacobowitz
2006-04-16 15:52 ` Nick Roberts [this message]
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=17474.11462.876311.964323@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=jingham@apple.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