From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PUSHED] "source", foreground execution commands, and target-async
Date: Tue, 25 Mar 2014 15:45:00 -0000 [thread overview]
Message-ID: <CADPb22QPqyUVDjPCjhMAXvXkmnpHYhjiRVbQM2CmExpD1j4_Cw@mail.gmail.com> (raw)
In-Reply-To: <1395750623-8054-1-git-send-email-palves@redhat.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.
prev parent reply other threads:[~2014-03-25 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 13:09 Pedro Alves
2014-03-25 15:45 ` Doug Evans [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADPb22QPqyUVDjPCjhMAXvXkmnpHYhjiRVbQM2CmExpD1j4_Cw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox