This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/20045] With mi-async on, -exec-continue outputs two (gdb) prompts
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 04 May 2016 22:44:15 +0000
- Subject: [Bug mi/20045] With mi-async on, -exec-continue outputs two (gdb) prompts
- Auto-submitted: auto-generated
- References: <bug-20045-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20045
--- Comment #5 from Pedro Alves <palves at redhat dot com> ---
> Anyway, it seems to me like this condition could only be
>
> if (sync_execution)
>
> Basically, if we are emulating a synchronous MI command, output the bogus
> (gdb). When using mi-async off, sync_execution will be false, so we will
> never output it. The result is this for mi-async off:
I think you meant "When using mi-async on, sync_execution will be false".
But when "maint set target-async off" (i.e., on targets that don't do async),
sync_execution will be off, even with sync commands.
This patch from the console series replaces that with a single enum that works
the same for async and sync targets, so probably fixes this:
https://sourceware.org/ml/gdb-patches/2016-02/msg00080.html
(haven't tried yet)
Though I think an easier and safe-for-7.11.1-even fix would be to call
target_can_async instead of target_is_async here.
--
You are receiving this mail because:
You are on the CC list for the bug.