This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PUSHED] "source", foreground execution commands, and target-async
- From: Doug Evans <dje at google dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 25 Mar 2014 08:45:15 -0700
- Subject: Re: [PUSHED] "source", foreground execution commands, and target-async
- Authentication-results: sourceware.org; auth=none
- References: <1395750623-8054-1-git-send-email-palves at redhat dot com>
On Tue, Mar 25, 2014 at 5:30 AM, Pedro Alves <palves@redhat.com> wrote:
> Sourcing a GDB script that runs foreground execution commands in
> succession fails if the target can async:
>
> Breakpoint 1, main () at ../../../src/gdb/testsuite/gdb.base/source-execution.c:36
> 36 func1 ();
> (gdb) source ../../../src/gdb/testsuite/gdb.base/source-execution.gdb
> ../../../src/gdb/testsuite/gdb.base/source-execution.gdb:21: Error in sourced command file:
> Cannot execute this command while the selected thread is running.
> (gdb) FAIL: gdb.base/source-execution.exp: source source-execution.gdb
>
> That is, after a foreground execution command, GDB moves on to the
> following command immediately before waiting for the previous command
> to complete.
>
> https://sourceware.org/ml/gdb-patches/2011-09/msg00037.html (b4a14fd0)
> addressed this for command lists, Python's gdb.execute, etc., but
> missed "source". Fixed now in the same way.
Thanks.