This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH]: Fix gdb's prompt for continue in TUI SingleKey mode
- From: Tom Tromey <tromey at redhat dot com>
- To: Stephane Carrez <stephane dot carrez at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 12 Nov 2012 08:44:26 -0700
- Subject: Re: [PATCH]: Fix gdb's prompt for continue in TUI SingleKey mode
- References: <CAJJuuYo440ttti=aWKXz9LkGvas6Ub2TWn14v6RBRBnVS+1cuw@mail.gmail.com>
>>>>> "Stephane" == Stephane Carrez <stephane.carrez@gmail.com> writes:
Stephane> Basically when we execute a gdb command, we must be in
Stephane> TUI_ONE_COMMAND_MODE (or TUI_COMMAND_MODE). We must restore
Stephane> the TUI_SINGLE_KEY_MODE only if we are not called from
Stephane> prompt_for_continue (I've used the check on 'immediate_quit'
Stephane> for that).
I don't know this code at all, but I think checking immediate_quit here
is weird. Partly this is because I think most uses of immediate_quit in
gdb are incorrect, and I'd like to try to phase them out -- but having
the TUI depend on it makes this harder. Is there some other way to do
it?
Tom