public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: Patch: operate-and-get-next
Date: Fri, 28 Sep 2001 10:27:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0109281024120.16046-100000@makita.cygnus.com> (raw)
In-Reply-To: <87snd7rzni.fsf@creche.redhat.com>

On 28 Sep 2001, Tom Tromey wrote:

> I looked into this a bit.  It turns out we already have some of the
> machinery in place to make it work correctly.  All that remains is
> making selected_frame_level_changed_hook do a little more work.

Did I mention that I, too, have a patch to fix this? Well, I have
something, but it's not good enough. Basically, we've got to rewrite the
command line to use some interface that allows for notifications.

The machinery for this in gdb is very, very twisted. (Be forewarned that
very soon gdbtk_update will be DEPRECATED: a nop.)

In any case, at one time I recall thinking that I knew of a way to "fix"
this, even if it is ugly. The problem is, we really only want to know when
the user changes the frame on us. NOT when gdb's internals change the
frame on us. This is the subtlety that I shoehorned around, adding event
notifiers to up/down command. :-)

Keith


  reply	other threads:[~2001-09-28 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28  9:15 Tom Tromey
2001-09-28  9:27 ` Keith Seitz
2001-09-28  9:36   ` Tom Tromey
2001-09-28  9:40     ` Keith Seitz
2001-09-28  9:54   ` John R. Moore
2001-09-28 10:12     ` Tom Tromey
2001-09-28 10:19   ` Tom Tromey
2001-09-28 10:27     ` Keith Seitz [this message]
2001-09-28 10:41       ` Tom Tromey
2001-09-28 11:03         ` 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=Pine.GSO.4.33.0109281024120.16046-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=tromey@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).