public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jon at beniston dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/12853] New: Unable to quit GDB if remote TCP connection is lost
Date: Tue, 07 Jun 2011 12:54:00 -0000 [thread overview]
Message-ID: <bug-12853-4717@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2011-06-07 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 12:54 jon at beniston dot com [this message]
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
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@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).