This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Flip the interpreter to synchronously wait for commands finishing, in command lists and similars
- From: Matt Rice <ratmice at gmail dot com>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 2 Sep 2011 16:28:15 -0700
- Subject: Re: Flip the interpreter to synchronously wait for commands finishing, in command lists and similars
- References: <201109021807.41992.pedro@codesourcery.com>
On Fri, Sep 2, 2011 at 10:07 AM, Pedro Alves <pedro@codesourcery.com> wrote:
>
> With this patch, synchronous execution commands (the regular step, next,
> etc., that is, those with an & suffixed) with a target running
> in async mode work correctly (AFAICT) with all current use cases. ? ?We
> can consider flipping on async on by default, and then incrementally
> convert specific paths to state machines, for new use cases, rather than
> delaying flipping on async on by default until _everything_ is converted
> into a state-machine.
I was hoping this might fix, (but doesn't seem to) the following case:
./gdb/gdb -ex 'set target-async on' -ex 'attach 7625' -ex 'continue'
./gdb/gdb -ex 'set target-async on' -ex 'attach 7625' -ex 'continue&'
both these commands exhibit:
Continuing.
Program received signal SIGSTOP, Stopped (signal).
.....
(gdb)
thus changing the behavior of '-ex continue' should we turn
target-async on by default.