This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 9/9] enable target-async
- From: Yao Qi <yao at codesourcery dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 1 Aug 2013 16:34:02 +0800
- Subject: Re: [PATCH v2 9/9] enable target-async
- References: <1375295281-7040-1-git-send-email-tromey at redhat dot com> <1375295281-7040-10-git-send-email-tromey at redhat dot com>
On 08/01/2013 02:28 AM, Tom Tromey wrote:
+/* Flag indicating whether the most recent command was executed via
+ the CLI interpreter. */
+int mi_last_was_cli;
+
In patch 6/9, a new field 'command_interp' is added to 'struct
thread_control_state', as below,
+
+ /* The interpreter that issued the execution command. NULL if the
+ thread was resumed as a result of a command applied to some other
+ thread (e.g., "next" with scheduler-locking off). */
+ struct interp *command_interp;
looks we can iterate over all threads, to check field command_interp to
know what interpreter is used by the previous command (assuming that
there should be only one thread whose command_interp is not NULL), so
that this flag 'mi_last_was_cli' can be removed?
--
Yao (éå)