From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19859 invoked by alias); 23 Aug 2012 16:44:37 -0000 Received: (qmail 19459 invoked by uid 22791); 23 Aug 2012 16:44:31 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Aug 2012 16:44:11 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0M9700500VPXQ700@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Thu, 23 Aug 2012 19:44:01 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M97005GEVTDFBB0@a-mtaout21.012.net.il>; Thu, 23 Aug 2012 19:44:01 +0300 (IDT) Date: Thu, 23 Aug 2012 16:44:00 -0000 From: Eli Zaretskii Subject: Re: further improve "handle" help string In-reply-to: <503659B8.9020107@redhat.com> To: Pedro Alves Cc: vapier@gentoo.org, dje@google.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83d32ha78l.fsf@gnu.org> References: <1344704080-24677-1-git-send-email-vapier@gentoo.org> <83has5jqex.fsf@gnu.org> <201208142158.42487.vapier@gentoo.org> <503659B8.9020107@redhat.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-08/txt/msg00674.txt.bz2 > Date: Thu, 23 Aug 2012 17:26:32 +0100 > From: Pedro Alves > CC: Eli Zaretskii , Doug Evans , > gdb-patches@sourceware.org > > On 08/15/2012 02:58 AM, Mike Frysinger wrote: > > On Tuesday 14 August 2012 14:10:14 Eli Zaretskii wrote: > >>> Date: Tue, 14 Aug 2012 10:34:10 -0700 > >>> From: Doug Evans > >>> Cc: gdb-patches@sourceware.org, Eli Zaretskii > >>> > >>> Ok with me, but I'd wait for Eli to check too. > >>> > >>> Thanks! > >> > >> I'm quite sure I already did. Mike, is that right? > > > > i've tweaked the signal wording, but i think the latest iteration covers > > everyone's concerns, so i'll merge this and we can fight over improving it > > further if need be ;) > > I'll byte ;-) > > I'd like to add a mention that you can specify more than one signal (though > not complicate and distract the main body of the text with this). I > use this occasionally. Text mostly borrowed from the sources. > > Tested on amd64 Fedora 17. > > (gdb) help handle > Specify how to handle signals. > Usage: handle SIGNAL [ACTIONS] > Args are signals and actions to apply to those signals. > If no actions are specified, the current settings for the specified signals > will be displayed instead. > > Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals > from 1-15 are allowed for compatibility with old versions of GDB. > Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5). > The special arg "all" is recognized to mean all signals except those > used by the debugger, typically SIGTRAP and SIGINT. > > Recognized actions include "stop", "nostop", "print", "noprint", > "pass", "nopass", "ignore", or "noignore". > Stop means reenter debugger if this signal happens (implies print). > Print means print a message if this signal happens. > Pass means let program see this signal; otherwise program doesn't know. > Ignore is a synonym for nopass and noignore is a synonym for pass. > Pass and Stop may be combined. > > Multiple signals may be specified. Signal numbers and signal names > may be interspersed with actions, with the actions being performed for > all signals cumulatively specified. > (gdb) OK, thanks.