This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb + remote qemu, Ctrl-C does not work
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb at sourceware dot org
- Cc: Tristan Gingold <gingold at adacore dot com>, dpc at ucore dot info, Mike Frysinger <vapier at gentoo dot org>
- Date: Wed, 2 Mar 2011 14:16:50 +0000
- Subject: Re: gdb + remote qemu, Ctrl-C does not work
- References: <AANLkTimvhnQs_4gTkaU_xfgjnm0G=Qkm-ZdzVYJ9nmfK@mail.gmail.com> <201103021249.34558.pedro@codesourcery.com> <0EA5A1E3-9098-457F-9334-74476345C908@adacore.com>
On Wednesday 02 March 2011 13:07:19, Tristan Gingold wrote:
> > Notice on your OP:
> >
> > Continuing.
> > ^CRemote communication error. Target disconnected.: Connection reset by peer.
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> IIRC we also had this issue. This was due to the fact that qemu exits before acking the packet.
>
I've seen that happen on a "quit/kill", due to the fact that
the 'k' packet (kill) does not require a reply.
But in this case, why would qemu exit at all before acking
the packet? This is about interrupting the target with ctrl-c, not
killing/quiting.
--
Pedro Alves