From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-41576-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 18622 invoked by alias); 19 Nov 2005 01:21:48 -0000
Received: (qmail 18592 invoked from network); 19 Nov 2005 01:21:43 -0000
Received: from unknown (202.80.33.51)   by sourceware.org with QMTP; 19 Nov 2005 01:21:43 -0000
Received: (qmail 2539 invoked from network); 19 Nov 2005 01:19:59 -0000
X-Anti-Virus: Message scanned for viruses by TVL
Received: from unknown (HELO [192.168.2.14]) ([202.80.36.15])           (envelope-sender <sjohnson@sakuraindustries.com>)           by mail.vanuatu.com.vu (qmail-ldap-1.03) with SMTP           for <kevinb@redhat.com>; 19 Nov 2005 01:19:59 -0000
Message-ID: <437E7DC6.4050309@sakuraindustries.com>
Date: Sat, 19 Nov 2005 10:57:00 -0000
From: Steven Johnson <sjohnson@sakuraindustries.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
MIME-Version: 1.0
To: Kevin Buettner <kevinb@redhat.com>
CC:  gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Add section on interrupts to remote protocol documentation
References: <20051117195224.32094bd5@ironwood.lan> <uwtj63wxm.fsf@gnu.org> 	 <20051118143309.73c45545@ironwood.lan> <8f2776cb0511181336l62caf79bsd91a5d123b4cd471@mail.gmail.com>
In-Reply-To: <8f2776cb0511181336l62caf79bsd91a5d123b4cd471@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2005-11/txt/msg00359.txt.bz2

Jim Blandy wrote:

>On 11/18/05, Kevin Buettner <kevinb@redhat.com> 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.
>
>
>  
>
Ditto.