From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Make "list" work again in TUI
Date: Sat, 15 Sep 2018 21:12:00 -0000 [thread overview]
Message-ID: <87musiqxbz.fsf@tromey.com> (raw)
In-Reply-To: <aa74137b-480f-2285-553b-36fb8b267912@redhat.com> (Pedro Alves's message of "Wed, 12 Sep 2018 13:31:41 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Something to keep in mind, though, is avoiding refreshes/updates
Pedro> caused by temporary thread stops while the target is running.
Pedro> E.g., if we have breakpoints with conditions that eval false,
Pedro> or e.g. a software watchpoint, we don't want the intermediate
Pedro> stops to cause a flurry of source window refreshes. I'm not
Pedro> sure whether that would invalidate what I said above, depends on
Pedro> when set_current_source_symtab_and_line is called, I suppose,
Pedro> but now I'm thinking that it probably does.
The troubling call is to set_current_sal_from_frame in normal_stop.
It seems like that one will be called frequently.
However one idea might be to have the TUI observer just set a flag, and
then continue to do the actual work in the prompt hook.
Pedro> That might suggest instead to start by seeing about trying to remove
Pedro> the select_source_symtab call from tui_refresh_frame_and_register_information.
Pedro> Why do we need that? Can we remove it and instead see about making
Pedro> tui_refresh_frame_and_register_information update the source window
Pedro> from get_current_source_symtab_and_line, if set_current_source_symtab_and_line
Pedro> was meanwhile called? I.e., refresh the source window if something changed
Pedro> "list"'s current source&line.
I'm going to give it a try.
Tom
next prev parent reply other threads:[~2018-09-15 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 14:32 Tom Tromey
2018-09-09 18:26 ` Tom Tromey
2018-09-12 12:20 ` Pedro Alves
2018-09-12 12:31 ` Pedro Alves
2018-09-15 21:12 ` Tom Tromey [this message]
2018-09-15 22:21 ` Tom Tromey
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=87musiqxbz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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