From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20246 invoked by alias); 26 Oct 2006 21:28:38 -0000 Received: (qmail 20234 invoked by uid 22791); 26 Oct 2006 21:28:37 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 26 Oct 2006 21:28:36 +0000 Received: (qmail 7209 invoked from network); 26 Oct 2006 21:28:34 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 26 Oct 2006 21:28:34 -0000 To: gdb@sourceware.org Subject: Re: [rfc/remote] Tell remote stubs which signals are boring References: <20061025212441.GA622@nevyn.them.org> <20061026211624.GA21239@nevyn.them.org> From: Jim Blandy Date: Thu, 26 Oct 2006 21:28:00 -0000 In-Reply-To: <20061026211624.GA21239@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 26 Oct 2006 17:16:24 -0400") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00273.txt.bz2 Daniel Jacobowitz writes: > On Thu, Oct 26, 2006 at 02:11:25PM -0700, Jim Blandy wrote: >> (Thanks, Mark, for asking about this!) Please don't use a space to >> mark the end of the packet name. At the moment, the remote protocol >> documentation uses spaces just for clarity; if they become meaningful, >> then we're going to have to revamp our manual notation --- again. >> >> The text in "Overview" suggests using ',', ';', or ':'. > > Typo in the documentation. The top of the general query packets page > is quite clear that it ought to be a colon, and so it is. Thanks. > >> > Each listed SIGNAL, using the same signal numbering used in >> >> I'd like to see "and syntax" added here --- I assume that's so? > > How much syntax is there to a single number? Well, the numbers might be in the passive voice. Or something. I had in mind fixed-width vs. variable-width. Fixed-width is used for signal numbers in the response packets, so I think there's room for confusion. Signal numbers in the step and continue packets are documented to be variable-width hex, which is safely permissive; all I'm suggesting is that those two words be added. I have run into width concerns working with other parts of the protocol (for example, with register values in T responses --- although that's target byte order so it's a bit different), so I think it's worth something to be explicit.