This is the mail archive of the
mailing list for the GDB project.
Re: MI non-stop interface details
- From: Pedro Alves <pedro at codesourcery dot com>
- To: "Marc Khouzam" <marc dot khouzam at ericsson dot com>
- Cc: "Vladimir Prus" <vladimir at codesourcery dot com>, gdb at sourceware dot org, "Pawel Piech" <pawel dot piech at windriver dot com>
- Date: Tue, 29 Apr 2008 20:11:28 +0100
- Subject: Re: MI non-stop interface details
- References: <6D19CA8D71C89C43A057926FE0D4ADAA042910AB@ecamlmw720.eamcs.ericsson.se>
A Tuesday 29 April 2008 19:56:15, Marc Khouzam wrote:
> For curiosity, what will happen to GDB's 'current thread' if that
> thread is continued, i.e., what if we have -exec-continue on a single
> thread as suggested above, and we issue two -exec-continue in a row?
This isn't stricly related to the current thread. What happens
if the frontend emits two '-exec-continue --thread="1"' ?
GDB will currently error out if a command tries to resume a
error ("Thread is already running");
Ignoring would also be a valid behaviour, I guess, although
an error condition is easier to define.