From: Andrew Cagney <ac131313@ges.redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] add selected-frame-level-changed events
Date: Tue, 27 Aug 2002 15:16:00 -0000 [thread overview]
Message-ID: <3D6BF9E1.4010005@ges.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208271420070.1408-100000@valrhona.uglyboxes.com>
> On Tue, 27 Aug 2002, Andrew Cagney wrote:
>
>
>> Why not put it in there anyway?
>
>
> You mean add a notification in select_frame? Because UIs don't care when
> GDB is temporarily switching frames for whatever reason. What matters is
> when something happens to cause the current frame to be changed and cause
> gdb and the MI client to get out of sync. As far as I know, this only
> happens via the command line frame commands (up, down, frame). There might
> be others, but I've never seen them.
Wonder what the TUI gets up to :-)
>> I think, not putting it in select_frame() is the part that needs the fixme.
>
>
> Right, that's what I meant. Sorry if I was vague. Ideally, we would like
> it in select_frame, but we cannot do that right now because the UI would
> be informed of billions of frame changes per step, especially if varobj is
> operating.
Ok. Can you just add comments explaining the above, especially in
select_frame(), so that people know why the call isn't yet there.
As for the unnecessary select frame calls, I guess ``we'' are working on
it. I suspect that varobj could do with an audit --- use FRAME_ID() and
frame parameterized versions of various functions.
Andrew
next prev parent reply other threads:[~2002-08-27 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 13:43 Keith Seitz
2002-08-27 14:20 ` Andrew Cagney
2002-08-27 14:40 ` Keith Seitz
2002-08-27 15:16 ` Andrew Cagney [this message]
2002-08-28 8:41 ` Keith Seitz
2002-08-28 8:51 ` Keith Seitz
2002-08-28 10:23 ` Andrew Cagney
2002-08-28 10:33 ` Keith Seitz
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=3D6BF9E1.4010005@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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