[Bug remote/12853] Unable to quit GDB if remote TCP connection is lost

["keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

Keith Seitz <keiths at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |keiths at redhat dot com
         AssignedTo|unassigned at sourceware    |keiths at redhat dot com
                   |dot org                     |

--- Comment #1 from Keith Seitz <keiths at redhat dot com> 2011-11-14 22:08:14 UTC ---
I cannot reproduce with the 7.3 branch (7.3.1-20111104-cvs) or CVS HEAD. I've
tried this on cygwin, too (Windows 2008 Server):

SHELL A:
$ gdbserver :1234 foo
Process foo created; pid = 1936
Listening on port 1234

SHELL B:
$ gdb -nx -q foo
(gdb) b main
Breakpoint 1 at 0x401196: file foo.c, line 6.
(gdb) tar remote :1234
Remote debugging using :1243
warning: Can not parse target XML description; XML support was disabled at
compile time
warning: Can not parser XML library list; XML support was disabled at compile
time
0x775e0005 in ?? ()
(gdb) c
Breakpoint 1, main () at foo.c:6
6   return 0;
(gdb)

SHELL C:
$ ps waux | grep gdbserver | kill `awk '{print $1}'`

SHELL B:
(gdb) quit
A debugging session is active.

     Inferior 1 [Remote target] will be killed.

Quit anyway? (y or n) y
qTStatus: remote connection closed
$ 

Can you verify any of this or provide me with a test that demonstrates the
problem better?

-- 
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.