From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19057 invoked by alias); 2 Mar 2011 14:24:01 -0000 Received: (qmail 19048 invoked by uid 22791); 2 Mar 2011 14:24:00 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,TW_QE X-Spam-Check-By: sourceware.org Received: from mel.act-europe.fr (HELO mel.act-europe.fr) (194.98.77.210) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Mar 2011 14:23:55 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id DD372CB036C; Wed, 2 Mar 2011 15:23:53 +0100 (CET) Received: from mel.act-europe.fr ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fj8qg0x6z7Mo; Wed, 2 Mar 2011 15:23:50 +0100 (CET) Received: from ulanbator.act-europe.fr (ulanbator.act-europe.fr [10.10.1.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mel.act-europe.fr (Postfix) with ESMTP id D180DCB037C; Wed, 2 Mar 2011 15:23:50 +0100 (CET) Subject: Re: gdb + remote qemu, Ctrl-C does not work Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Tristan Gingold In-Reply-To: <201103021416.50765.pedro@codesourcery.com> Date: Wed, 02 Mar 2011 14:24:00 -0000 Cc: gdb@sourceware.org, dpc@ucore.info, Mike Frysinger Content-Transfer-Encoding: quoted-printable Message-Id: <75F42F18-B543-47F3-8A1B-B8A9748268C1@adacore.com> References: <201103021249.34558.pedro@codesourcery.com> <0EA5A1E3-9098-457F-9334-74476345C908@adacore.com> <201103021416.50765.pedro@codesourcery.com> To: Pedro Alves X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00018.txt.bz2 On Mar 2, 2011, at 3:16 PM, Pedro Alves wrote: > On Wednesday 02 March 2011 13:07:19, Tristan Gingold wrote: >>> Notice on your OP: >>>=20 >>> Continuing. >>> ^CRemote communication error. Target disconnected.: Connection reset b= y peer. >>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^= ^^^^^^ >>=20 >> IIRC we also had this issue. This was due to the fact that qemu exits b= efore acking the packet. >>=20 >=20 > I've seen that happen on a "quit/kill", due to the fact that > the 'k' packet (kill) does not require a reply. >=20 > 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. Right. Why I was so confused ? :-) Tristan.