From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Be lazy about refreshing the windows in tui_show_frame_info (PR tui/13378)
Date: Tue, 30 Jun 2015 17:26:00 -0000 [thread overview]
Message-ID: <5592D150.6080201@redhat.com> (raw)
In-Reply-To: <1435683072-7810-1-git-send-email-patrick@parcs.ath.cx>
On 06/30/2015 05:51 PM, Patrick Palka wrote:
> [ This version just changes tui_set_locator_info as you suggested. ]
>
> tui_show_frame_info is responsible for updating the visible windows
> following a change in frame information (that being the currently
> selected frame, PC, line number, etc). Currently it always redraws and
> refreshes each window even if frame information has not changed. This
> behavior is inefficient and helps contribute to the occassional
> flickering of the TUI as described in the mentioned PR.
>
> This patch makes tui_show_frame_info refresh the windows only if frame
> information has changed. Determining whether frame information has
> changed is done indirectly by determining whether the locator has
> changed. This approach is convenient and yet sensible because the
> locator contains all the relevant info we need to check anyway: the
> current PC, the line number, the name of the executable and the name of
> the current function. Probably only the PC is really necessary to
> check, but it doesn't hurt to check every field.
>
> Effectively, with this patch, consecutive calls to select_frame with the
> same frame/PC no longer cause TUI's frame information to be updated
> multiple times.
>
> gdb/ChangeLog:
>
> * tui/tui-stack.c (tui_set_locator_info): Change prototype to
> return an int instead of void. Return whether the locator
> window has changed.
> (tui_show_frame_info): If the locator info has not changed, then
> bail out early to avoid refreshing the windows.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-06-30 17:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 2:35 [PATCH 1/3] Correctly initialize the TUI locator window Patrick Palka
2015-06-27 2:35 ` [PATCH 3/3] Replace TUI's select_frame hook (PR tui/13378) Patrick Palka
2015-06-27 2:50 ` Patrick Palka
2015-06-30 9:32 ` Pedro Alves
2015-06-30 12:16 ` Patrick Palka
2015-06-30 12:37 ` Patrick Palka
2015-06-30 14:08 ` Pedro Alves
2015-06-30 14:54 ` Patrick Palka
2015-06-30 14:56 ` Patrick Palka
2015-06-30 15:12 ` Patrick Palka
2015-06-30 15:47 ` Pedro Alves
2015-06-30 16:40 ` Patrick Palka
2015-06-30 17:07 ` Pedro Alves
2015-06-30 17:11 ` Patrick Palka
2015-06-30 17:32 ` Pedro Alves
2015-06-30 17:49 ` Patrick Palka
2015-07-01 12:40 ` Patrick Palka
2015-06-30 13:23 ` Pedro Alves
2015-06-30 14:03 ` Patrick Palka
2015-06-27 2:35 ` [PATCH 2/3] Be lazy about refreshing the windows in tui_show_frame_info " Patrick Palka
2015-06-30 2:32 ` [PATCH] " Patrick Palka
2015-06-30 14:27 ` Pedro Alves
2015-06-30 14:45 ` Patrick Palka
2015-06-30 15:11 ` Pedro Alves
2015-06-30 15:15 ` Patrick Palka
2015-06-30 16:51 ` [PATCH 2/3] " Patrick Palka
2015-06-30 17:26 ` Pedro Alves [this message]
2015-06-30 8:36 ` [PATCH 1/3] Correctly initialize the TUI locator window Pedro Alves
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=5592D150.6080201@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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