From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Sterling Augustine <saugustine@google.com>
Subject: Re: [PATCH - TUI and Insight Related] Fix for PR13378
Date: Sat, 12 Nov 2011 00:28:00 -0000 [thread overview]
Message-ID: <201111120028.09459.pedro@codesourcery.com> (raw)
In-Reply-To: <CAEG7qUwxs5K=NOybj_oX2LU7NG5iE517QS3+1gAGgoAuO055aw@mail.gmail.com>
On Friday 11 November 2011 20:53:59, Sterling Augustine wrote:
> Hi,
>
> Enclosed is a very simple patch which fixes the annoying TUI-updating
> issue described in
> http://sourceware.org/bugzilla/show_bug.cgi?id=13378.
>
> It simply eliminates a call to
> deprecated_selected_frame_level_changed_hook. This hook has been
> deprecated for many years, so one would think it's clients have had
> time to remove the dependency.
Sorry, this approach is backwards. We should stop TUI from
installing the hook first instead. Then when all users have
disappeared, we can eliminate the hook.
> After using it locally for a week now,
> I see no ill effects in TUI. stopping at breakpoints, up, down, and
> the other stuff all work fine for me. However, the testsuite is, err,
> incomplete on this feature.
I've tried it, and that's unfortunately not true -- TUI no longer
reacts to up/down.
The right fix is adding a new observer for when the user changes the
frame, and make TUI use it instead of this hook that triggers all
too often. I thought MI had such an observer, but I guess that
was some discussion that never got anywhere or a patch that never
got in.
--
Pedro Alves
prev parent reply other threads:[~2011-11-12 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 20:54 Sterling Augustine
2011-11-11 21:17 ` Keith Seitz
2011-11-12 0:28 ` Pedro Alves [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=201111120028.09459.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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