Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] gdb.texinfo
Date: Sun, 15 Oct 2006 21:36:00 -0000	[thread overview]
Message-ID: <uslhpqn2f.fsf@gnu.org> (raw)
In-Reply-To: <17713.20647.37355.257609@kahikatea.snap.net.nz> (message from 	Nick Roberts on Sun, 15 Oct 2006 10:03:35 +1300)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 15 Oct 2006 10:03:35 +1300
> Cc: gdb-patches@sources.redhat.com
> 
> There are many similar discrepancies in the manual
> 
>   `info signals'
>   `info handle'
> 
> should be:
> 
>   `info signals [N]'
>   `info handle [N]'

Fixed.

>   `handle SIGNAL KEYWORDS...'
> 
> should be:
> 
>   `handle SIGNAL [KEYWORDS...]'

Fixed.

> Incidentally `handle SIGINT' asks 
> 
>   SIGINT is used by the debugger.
>   Are you sure you want to change it? (y or n) 
> 
> even though it doesn't appear to change anything

Sorry, I'm not following: what do you mean by ``doesn't appear to
change anything''?

> info breakpoints [N]
> 
> doesn't describe what [N] does...

Fixed.  Here's what I committed:


2006-10-15  Eli Zaretskii  <eliz@gnu.org>

	* gdb.texinfo (Signals, Set Breaks, Set Watchpoints): Document optional
	arguments to `info signals'  `handle', `info breakpoints', and
	`info watchpoints'.

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.359
diff -u -r1.359 gdb.texinfo
--- gdb/doc/gdb.texinfo	15 Oct 2006 21:19:24 -0000	1.359
+++ gdb/doc/gdb.texinfo	15 Oct 2006 21:32:31 -0000
@@ -2985,7 +2985,9 @@
 @itemx info break @r{[}@var{n}@r{]}
 @itemx info watchpoints @r{[}@var{n}@r{]}
 Print a table of all breakpoints, watchpoints, and catchpoints set and
-not deleted, with the following columns for each breakpoint:
+not deleted.  Optional argument @var{n} means print information only
+about the specified breakpoint (or watchpoint or catchpoint).  For
+each breakpoint, following columns are printed:
 
 @table @emph
 @item Breakpoint Numbers
@@ -3135,7 +3137,7 @@
 Set a watchpoint that will break when @var{expr} is either read from
 or written into by the program.
 
-@kindex info watchpoints
+@kindex info watchpoints @r{[}@var{n}@r{]}
 @item info watchpoints
 This command prints a list of watchpoints, breakpoints, and catchpoints;
 it is the same as @code{info break} (@pxref{Set Breaks}).
@@ -4130,15 +4132,19 @@
 handle each one.  You can use this to see the signal numbers of all
 the defined types of signals.
 
+@item info signals @var{sig}
+Similar, but print information only about the specified signal number.
+
 @code{info handle} is an alias for @code{info signals}.
 
 @kindex handle
-@item handle @var{signal} @var{keywords}@dots{}
+@item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]}
 Change the way @value{GDBN} handles signal @var{signal}.  @var{signal}
 can be the number of a signal or its name (with or without the
 @samp{SIG} at the beginning); a list of signal numbers of the form
 @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the
-known signals.  The @var{keywords} say what change to make.
+known signals.  Optional arguments @var{keywords}, described below,
+say what change to make.
 @end table
 
 @c @group


  parent reply	other threads:[~2006-10-15 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  0:24 Nick Roberts
2006-10-14 18:35 ` Eli Zaretskii
2006-10-14 21:06   ` Nick Roberts
2006-10-15  4:34     ` Eli Zaretskii
2006-10-15 21:36     ` Eli Zaretskii [this message]
2006-10-15 21:51       ` Nick Roberts

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=uslhpqn2f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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