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

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

[jon at beniston dot com]

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.

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

[jon at beniston dot com]

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

jon at beniston dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Host|                            |windows 7 / cygwin

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

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

[keiths at redhat dot com]

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.

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

[keiths at redhat dot com]

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

Keith Seitz <keiths at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #2 from Keith Seitz <keiths at redhat dot com> 2012-08-28 16:44:39 UTC ---
It's almost ten months. This still works, as described, on CVS HEAD
(7.5.50.20120828-cvs) and the 7.5 branch. I'm closing this bug.

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

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

[jan.smets@alcatel-lucent.com]

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

Jan Smets <jan.smets@alcatel-lucent.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |jan.smets@alcatel-lucent.co
                   |                            |m
         Resolution|WORKSFORME                  |---

--- Comment #3 from Jan Smets <jan.smets@alcatel-lucent.com> ---
Can someone please re-investigate? I'm having the same issue with 7.5

1) connect to a remote target
2) attach to a process
3) disconnect/reset the remote target
4) watch the timeout
5) try detaching or quit gdb

(gdb) attach 165209617
Attaching to process 165209617
[New Thread 165209617.165209617]
0x07ab29bc in __memPoolInit ()
(gdb) c
Continuing.
^C
[Thread 165209617.165209617] #1 stopped.
0x07ab29bc in __memPoolInit ()
Ignoring packet error, continuing...
Stopping Thread 165209617.165209617 failed: timeout
(gdb) Ignoring packet error, continuing...
Stopping Thread 165209617.165209617 failed: timeout
(gdb) (gdb)
Continuing.
Cannot execute this command while the selected thread is running.
(gdb) 
(gdb) exit
Undefined command: "exit".  Try "help".
(gdb) quit
A debugging session is active.

        Inferior 1 [process 165209617] will be detached.

Quit anyway? (y or n) y

Ignoring packet error, continuing...
Bogus trace status reply from target: timeout
(gdb) 
A debugging session is active.

        Inferior 1 [process 165209617] will be detached.
.... (can't get out of GDB!!)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[jan.smets@alcatel-lucent.com]

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

Jan Smets <jan.smets@alcatel-lucent.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Host|windows 7 / cygwin          |windows 7 / cygwin / linux

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[jan.smets@alcatel-lucent.com]

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

Jan Smets <jan.smets@alcatel-lucent.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|7.2                         |7.5

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[palves at redhat dot com]

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |palves at redhat dot com
         Resolution|---                         |WORKSFORME

--- Comment #4 from Pedro Alves <palves at redhat dot com> ---
(In reply to Jan Smets from comment #3)
> Can someone please re-investigate? I'm having the same issue with 7.5

You'll most probably need a more recent GDB.

Keith mentioned 7.5.50.20120828-cvs
(future 7.6), and the 7.5 branch (what ended up as 7.5.1).

In any case 7.5 is old by now.  Please reopen if you can reproduce it with a
7.7, or ideally a recent snapshot or git head (we're not that far from 7.8
now).

-- 
You are receiving this mail because:
You are on the CC list for the bug.