From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32654 invoked by alias); 26 Oct 2006 01:40:37 -0000 Received: (qmail 32645 invoked by uid 22791); 26 Oct 2006 01:40:36 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 26 Oct 2006 01:40:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GcuEN-0002N9-1w; Wed, 25 Oct 2006 21:40:27 -0400 Date: Thu, 26 Oct 2006 01:40:00 -0000 From: Daniel Jacobowitz To: David Daney Cc: gdb@sourceware.org Subject: Re: [rfc/remote] Tell remote stubs which signals are boring Message-ID: <20061026014027.GA9023@nevyn.them.org> Mail-Followup-To: David Daney , gdb@sourceware.org References: <20061025212441.GA622@nevyn.them.org> <453FEB98.8090202@avtrex.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <453FEB98.8090202@avtrex.com> User-Agent: Mutt/1.5.13 (2006-08-11) 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/msg00250.txt.bz2 On Wed, Oct 25, 2006 at 03:56:24PM -0700, David Daney wrote: > > Use of this packet is controlled by the `set remote pass-signals' > > command (*note set remote pass-signals: Remote configuration.). > > This packet is not probed by default; the remote stub must request > > it, by supplying an appropriate `qSupported' response (*note > > qSupported::). > > Does this mean that you have to issue a 'set remote pass-signals' > command, or is it done automatically for 'handle noprint nostop pass' if > the remote stub supports it? > > Not being that familiar with the remote protocol, it is unclear to me. It will just work. The conversation goes like this: -> qSupported: # Whatcha got? <- PacketSize=4000;QPassSignals+ # I got big buffers. And stuff. -> QPassSignals:e;10;14 # Don't care about all these. <- OK # OK, I don't care. -> vCont:c # RUN! The "set remote" command is only for overrides. Honestly, I've been thinking of removing the override commands, or moving them into maint somewhere; they're half the trouble in adding and documenting a new command, and we're just adding them for consistency at this point. I don't think they're really useful except for testing. -- Daniel Jacobowitz CodeSourcery