This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug remote/12853] New: Unable to quit GDB if remote TCP connectionis lost


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

           Summary: Unable to quit GDB if remote TCP connection is lost
           Product: gdb
           Version: 7.2
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
        AssignedTo: unassigned@sourceware.org
        ReportedBy: jon@beniston.com


If using a TCP remote connection (E.g. tar ext localhost:1234), if the target
connection is lost for some reason, it is no longer possible to quit GDB.

(gdb) quit
A debugging session is active.

        Inferior 1 [Remote target] will be killed.

Quit anyway? (y or n) y
putpkt: write failed: Connection reset by peer.
(gdb)

i.e. you get the putpkt error message, and then get returned to the prompt.

Pressing ctrl-c several times just results in:

(gdb) Quit
(gdb) Quit
(gdb) Quit...

being printed.

This is occuring on a Windows 7 64-bit / Cygwin system.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]