[Bug remote/15275] New: gdb quit command fails if remote serial linkis broken

["gareth at blacksphere dot co.nz" <sourceware-bugzilla at sourceware dot org>]

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

             Bug #: 15275
           Summary: gdb quit command fails if remote serial link is broken
           Product: gdb
           Version: 7.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
        AssignedTo: unassigned@sourceware.org
        ReportedBy: gareth@blacksphere.co.nz
    Classification: Unclassified


If debugging with a remote connection over a serial link and the link is
disconnected, say by disconnecting USB serial port, the GDB quit command no
longer works.  GDB must be forcibly killed.  The MI -gdb-exit command does
still work.

This is tested on a Debian Wheezy amd64 host system with GDB 7.5.1 for
arm-none-eabi target.

This may be a duplicate of bug 11221 and/or 12853 as the symptoms are very
similar.

(gdb) 
tar ext /dev/ttyACM0
&"tar ext /dev/ttyACM0\n"
~"Remote debugging using /dev/ttyACM0\n"
^done
(gdb) 
set debug remote 1
&"set debug remote 1\n"
^done
(gdb) 
quit
&"quit\n"
&"Sending packet: $qTStatus#49..."
&"putpkt: write failed: Input/output error.\n"
^error,msg="putpkt: write failed: Input/output error."
(gdb) 
-gdb-exit
^exit

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