From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30689 invoked by alias); 18 Nov 2005 21:36:43 -0000 Received: (qmail 30681 invoked by uid 22791); 18 Nov 2005 21:36:41 -0000 Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.207) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 18 Nov 2005 21:36:41 +0000 Received: by zproxy.gmail.com with SMTP id l1so306694nzf for ; Fri, 18 Nov 2005 13:36:39 -0800 (PST) Received: by 10.36.13.10 with SMTP id 10mr197109nzm; Fri, 18 Nov 2005 13:36:39 -0800 (PST) Received: by 10.37.2.35 with HTTP; Fri, 18 Nov 2005 13:36:39 -0800 (PST) Message-ID: <8f2776cb0511181336l62caf79bsd91a5d123b4cd471@mail.gmail.com> Date: Fri, 18 Nov 2005 22:07:00 -0000 From: Jim Blandy To: Kevin Buettner Subject: Re: [rfa/doc] Add section on interrupts to remote protocol documentation Cc: gdb-patches@sources.redhat.com In-Reply-To: <20051118143309.73c45545@ironwood.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051117195224.32094bd5@ironwood.lan> <20051118143309.73c45545@ironwood.lan> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00348.txt.bz2 On 11/18/05, Kevin Buettner wrote: > +@samp{Ctrl-C}, on the other hand, is defined and implemented for all > +transport mechanisms. It is represented by sending the single byte > +@code{0x03} without any of the usual packet overhead described in in > +the Overview section (@pxref{Overview}). When a @code{0x03} byte is > +transmitted as part of a packet, it is considered to be packet data > +and does @emph{not} represent an interrupt. E.g., an @samp{X} packet > +(@pxref{X packet}, used for binary downloads, may include an unescaped > +@code{0x03} as part of its packet. Yep, that's pretty explicit. Fine with me.