[Bug gdb/14236] New: Cannot continue in background with target-asyncafter interrupting

["owlberteinstein at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=14236

             Bug #: 14236
           Summary: Cannot continue in background with target-async after
                    interrupting
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: owlberteinstein@gmail.com
    Classification: Unclassified


When using target-async, continuing immediately after interrupting fails. I
discovered this while experimenting with the Python API. time.sleep()ing for
any amount of time doesn't fix the problem.

Using gdb 7.4.1 on Arch Linux.

Example session exhibiting the bug (yes, it looked exactly like that):

(gdb) define buggy
Type commands for definition of "buggy".
End with a line saying just "end".
>continue &
>interrupt
>continue &
>end
(gdb) buggy
Cannot execute this command while the selected thread is running.
(gdb) 
Program received signal SIGINT, Interrupt.
0x00007fc11e5fbb5d in nanosleep () from /lib/libc.so.6

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.