From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@gnu.org>
Cc: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: How does GDB/MI give the current frame
Date: Sat, 26 Jun 2004 14:59:00 -0000 [thread overview]
Message-ID: <20040626145935.GA26129@nevyn.them.org> (raw)
In-Reply-To: <16605.15641.474398.42157@nick.uklinux.net>
On Sat, Jun 26, 2004 at 10:08:41AM +0100, Nick Roberts wrote:
>
> Daniel Jacobowitz writes:
> DJ>
> DJ> Why not use -stack-info-frame?
>
> Because AFAIK this MI command has not been implemented (yet).
So it hasn't! Silly me, I was fooled by it being documented in the
manual.
> Andrew Cagney writes:
>
> AC> When the user does "up", "down", the debugger should generate a selected
> AC> CLI frame changed event (it currently doesn't). If the GUI so chooses,
> AC> it can track the users "selected" frame, by responding to these events.
>
> I don't know what a selected CLI frame changed event is but up, down, and
> frame generate MI output, so I imagine its just a case of hooking
> -stack-info-frame and -stack-select-frame to that output. I will try to do
> this if you think it's appropriate.
I think that Andrew's answering a related question: for debuggers which
allow entry of console commands, the interface needs a way to update
its windows when the user types "up". Since you're just interested in
MI at the moment, I suspect that filling in -stack-info-frame is the
way to go.
I'm not sure whether -stack-select-frame should have output or not.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-26 14:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 22:54 Nick Roberts
2004-06-24 23:17 ` Daniel Jacobowitz
2004-06-26 9:10 ` Nick Roberts
2004-06-26 14:59 ` Daniel Jacobowitz [this message]
2004-06-27 2:12 ` Andrew Cagney
2004-06-30 20:47 ` Alain Magloire
[not found] ` <200406302047.QAA29956@smtp.ott.qnx.com>
2004-07-02 17:29 ` Nick Roberts
2004-07-08 22:15 ` Andrew Cagney
2004-07-08 23:07 ` Alain Magloire
2004-07-11 22:49 ` Nick Roberts
2004-07-12 14:24 ` Andrew Cagney
2004-07-12 20:09 ` Nick Roberts
2004-07-15 14:48 ` Andrew Cagney
2004-07-15 19:50 ` Nick Roberts
2004-07-15 20:19 ` Jason Molenda
2004-07-15 21:08 ` Jason Molenda
2004-07-16 14:12 ` Alain Magloire
2004-07-16 14:08 ` Alain Magloire
[not found] ` <200407161404.KAA02192@smtp.ott.qnx.com>
2004-07-18 21:07 ` Nick Roberts
2004-07-26 21:31 ` Andrew Cagney
[not found] ` <200407082307.TAA09285@smtp.ott.qnx.com>
2004-07-11 22:49 ` Nick Roberts
2004-07-12 18:30 ` Alain Magloire
[not found] ` <200407121751.NAA24942@smtp.ott.qnx.com>
2004-07-14 4:00 ` Nick Roberts
2004-06-25 15:12 ` 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=20040626145935.GA26129@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@gnu.org \
/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).