aboutsummaryrefslogtreecommitdiff
path: root/gdb/addrmap.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2023-01-05 12:26:09 +0000
committerAndrew Burgess <aburgess@redhat.com>2023-01-27 16:20:10 +0000
commit99c15700fd47e59a14d6338fda7aeadf5ba480f3 (patch)
treee833e5344268049070dc4c99b80f0873e622cf0b /gdb/addrmap.c
parentd2a5ea5622ec7a2a3e255186c88d69812f148913 (diff)
downloadgdb-99c15700fd47e59a14d6338fda7aeadf5ba480f3.zip
gdb-99c15700fd47e59a14d6338fda7aeadf5ba480f3.tar.gz
gdb-99c15700fd47e59a14d6338fda7aeadf5ba480f3.tar.bz2
gdb/tui: avoid extra refresh_window on vertical scroll
While working on the previous couple of patches I noticed that when I scroll the src and asm windows vertically, I get two refresh_window calls. The two calls can be traced back to tui_source_window_base::update_source_window_as_is, in here we call show_source_content, which calls refresh_window, and then update_exec_info, which also calls refresh_window. In this commit I propose making the refresh_window call in update_exec_info optional. In update_source_window_as_is I'll then call update_exec_info before calling show_source_content, and pass a flag to update_exec_info to defer the refresh. There are places where update_exec_info is used without any subsequent refresh_window call (e.g. when a breakpoint is updated), so update_exec_info does not to call refresh_window in some cases, which is why I'm using a flag to control the refresh. With this changes I'm now only seeing a single refresh_window call for each vertical scroll. There should be no user visible changes after this commit.
Diffstat (limited to 'gdb/addrmap.c')
0 files changed, 0 insertions, 0 deletions