[Bug gdb/16809] interrupt -a

["xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16809

--- Comment #11 from Doug Evans <xdje42 at gmail dot com> ---
(In reply to dilyan.palauzov@aegee.org from comment #10)
> However, when I do "interrupt -a", gdb prints the prompt, followed by
> information about individual threads, and eventually puts the cursor on a
> very biginning of new line (not immediately after the prompt).  This unclear
> state was the reason to press several times <RET> and to discover this bug.
> 
> Does pagination still break non-stop?  If not, remove the relevant text from
> gdb/doc/gdb.texinfo , node "Non-Stop mode", line 5781-5784.

The issue here is that messages can be printed by gdb (e.g. to report thread
state changes) even while gdb is at the prompt waiting for user input.  This is
gdb's async mode and it's now the default.  The "interrupt" command has a bug
in that it operates asynchronously (as if you had added a "&") by default.
What should happen is that "interrupt" or "interrupt -a" without an "&" should
operate synchronously and not print the gdb prompt until the command has
succeeded (just like commands that resume the inferior like run, continue,
etc.).

-- 
You are receiving this mail because:
You are on the CC list for the bug.