This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: further improve "handle" help string


> Date: Thu, 23 Aug 2012 17:26:32 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: Eli Zaretskii <eliz@gnu.org>, Doug Evans <dje@google.com>,
>         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 <dje@google.com>
> >>> Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
> >>>
> >>> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]