public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.smets@alcatel-lucent.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/12853] Unable to quit GDB if remote TCP connection is lost
Date: Wed, 21 May 2014 11:50:00 -0000	[thread overview]
Message-ID: <bug-12853-4717-A1Q0C6cXVV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12853-4717@http.sourceware.org/bugzilla/>

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.


  parent reply	other threads:[~2014-05-21 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 12:54 [Bug remote/12853] New: " jon at beniston dot com
2011-06-07 12:54 ` [Bug remote/12853] " jon at beniston dot com
2011-11-14 22:08 ` keiths at redhat dot com
2012-08-28 16:44 ` keiths at redhat dot com
2014-05-21 11:50 ` jan.smets@alcatel-lucent.com [this message]
2014-05-21 11:51 ` jan.smets@alcatel-lucent.com
2014-05-21 11:54 ` jan.smets@alcatel-lucent.com
2014-05-21 23:23 ` palves at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-12853-4717-A1Q0C6cXVV@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).