This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug remote/11221] New: Interrupting gdbserver makes quit in gdb not work
- From: "timo dot suoranta at acrodea dot co dot jp" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 26 Jan 2010 13:35:12 -0000
- Subject: [Bug remote/11221] New: Interrupting gdbserver makes quit in gdb not work
- Reply-to: sourceware-bugzilla at sourceware dot org
When I start gdbserver, connect with gdb, interrupt gdbserver (ctrl-c), quit
command does not work - gdb does not exit. Meanwhile -gdb-exit manages to exit
gdb. "Disconnected tracing related regression"?
(gdb)
set debug remote 1
&"set debug remote 1\n"
^done
(gdb)
quit
&"quit\n"
&"Sending packet: $qTStatus#49..."
&"Remote communication error: No such file or directory.\n"
^error,msg="Remote communication error: No such file or directory."
(gdb)
quit
&"quit\n"
&"Sending packet: $qTStatus#49..."
&"putpkt: write failed: No error.\n"
^error,msg="putpkt: write failed: No error."
(gdb)
--
Summary: Interrupting gdbserver makes quit in gdb not work
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: remote
AssignedTo: unassigned at sourceware dot org
ReportedBy: timo dot suoranta at acrodea dot co dot jp
CC: gdb-prs at sourceware dot org
GCC build triplet: i686-pc-mingw32
GCC host triplet: i686-pc-mingw32
GCC target triplet: arm-eabi-linux
http://sourceware.org/bugzilla/show_bug.cgi?id=11221
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.