From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14289 invoked by alias); 4 Nov 2007 07:23:43 -0000 Received: (qmail 14276 invoked by uid 22791); 4 Nov 2007 07:23:42 -0000 X-Spam-Check-By: sourceware.org Received: from hu-out-0506.google.com (HELO hu-out-0506.google.com) (72.14.214.224) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 04 Nov 2007 07:23:39 +0000 Received: by hu-out-0506.google.com with SMTP id 22so542787hug for ; Sun, 04 Nov 2007 00:23:36 -0700 (PDT) Received: by 10.67.122.10 with SMTP id z10mr4709807ugm.1194161015589; Sun, 04 Nov 2007 00:23:35 -0700 (PDT) Received: from localhost ( [85.231.134.78]) by mx.google.com with ESMTPS id 36sm4445783ugb.2007.11.04.00.23.34 (version=SSLv3 cipher=OTHER); Sun, 04 Nov 2007 00:23:35 -0700 (PDT) Date: Sun, 04 Nov 2007 07:23:00 -0000 From: Simon Kagstrom To: Daniel Jacobowitz Cc: gdb@sourceware.org Subject: Re: Interrupt packets in the remote protocol Message-ID: <20071104082645.06407e3b@localhost> In-Reply-To: <20071104030809.GA8183@caradoc.them.org> References: <20071103182847.54afb758@localhost> <20071104030809.GA8183@caradoc.them.org> X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: 2007-11/txt/msg00024.txt.bz2 On Sat, 3 Nov 2007 23:08:09 -0400 Daniel Jacobowitz wrote: > On Sat, Nov 03, 2007 at 06:28:47PM +0100, Simon Kagstrom wrote: > > The server mostly works now except for interrupts (Ctrl-C in GDB). > > It looks like the interrupt packets (plain 0x03) are never sent. A > > log with 'set debug remote 1' looks as follows: > > How sure are you of this? The Ctrl-C packet won't show up directly in > the log, because it's not a "packet" as such. It doesn't get the $ or > #CHECKSUM; it's just a \003. OK, I ran wireshark and dumped the traffic, and I can see now that 0x03 is sent. So the problem is on my side. Thanks for the help! -- // Simon