This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/14236] Cannot continue in background with target-async after interrupting
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 22 Mar 2014 00:05:15 +0000
- Subject: [Bug gdb/14236] Cannot continue in background with target-async after interrupting
- Auto-submitted: auto-generated
- References: <bug-14236-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14236
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at google dot com
--- Comment #1 from dje at google dot com ---
I believe what's going on here is that the "interrupt" command is either
designed wrong or implemented wrong.
There is an implicit "&" in "interrupt".
IOW, you typed "interrupt" but gdb interprets it as "interrupt &".
IOW, "interrupt" is just a request to stop a thread, it doesn't actually wait
for the thread to stop.
Thus the subsequent "continue &" command is done before the thread has stopped,
hence the error.
I agree there's a bug here somewhere.
An implicit "&" is confusing, thus IMO that's at least one bug.
A request to stop a thread should be "interrupt &".
"interrupt" by itself should wait until the thread has stopped.
--
You are receiving this mail because:
You are on the CC list for the bug.