From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: vapier@gentoo.org, dje@google.com, gdb-patches@sourceware.org
Subject: Re: further improve "handle" help string
Date: Thu, 23 Aug 2012 16:44:00 -0000 [thread overview]
Message-ID: <83d32ha78l.fsf@gnu.org> (raw)
In-Reply-To: <503659B8.9020107@redhat.com>
> 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.
next prev parent reply other threads:[~2012-08-23 16:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 16:55 [PATCH] gdb: improve usage strings Mike Frysinger
2012-08-11 17:16 ` Eli Zaretskii
2012-08-11 17:36 ` Mike Frysinger
2012-08-11 17:52 ` Eli Zaretskii
2012-08-11 18:08 ` Mike Frysinger
2012-08-14 15:08 ` Tom Tromey
2012-08-12 5:06 ` Doug Evans
2012-08-12 5:10 ` Mike Frysinger
2012-08-12 17:35 ` Eli Zaretskii
2012-08-13 2:06 ` [PATCH v2] " Mike Frysinger
2012-08-13 20:29 ` Doug Evans
2012-08-14 5:13 ` Mike Frysinger
2012-08-23 11:11 ` Pedro Alves
2012-08-14 5:29 ` [PATCH v3] " Mike Frysinger
2012-08-14 17:34 ` Doug Evans
2012-08-14 18:10 ` Eli Zaretskii
2012-08-15 1:58 ` Mike Frysinger
2012-08-15 7:22 ` Regression for gdb.base/help.exp [Re: [PATCH v3] gdb: improve usage strings] Jan Kratochvil
2012-08-15 16:25 ` Mike Frysinger
2012-08-15 16:27 ` Doug Evans
2012-08-20 4:29 ` Sergio Durigan Junior
2012-08-17 3:06 ` Mike Frysinger
2012-08-23 16:26 ` further improve "handle" help string Pedro Alves
2012-08-23 16:44 ` Eli Zaretskii [this message]
2012-08-23 17:18 ` Mike Frysinger
2012-08-23 17:38 ` Pedro Alves
2012-08-23 11:11 ` [PATCH v3] gdb: improve usage strings Pedro Alves
2012-08-23 16:45 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d32ha78l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox