From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32564 invoked by alias); 15 Oct 2006 21:36:14 -0000 Received: (qmail 32553 invoked by uid 22791); 15 Oct 2006 21:36:13 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 15 Oct 2006 21:36:11 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-5-198.inter.net.il [83.130.5.198]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id EXU66435 (AUTH halo1); Sun, 15 Oct 2006 23:35:59 +0200 (IST) Date: Sun, 15 Oct 2006 21:36:00 -0000 Message-Id: From: Eli Zaretskii To: Nick Roberts CC: gdb-patches@sources.redhat.com In-reply-to: <17713.20647.37355.257609@kahikatea.snap.net.nz> (message from Nick Roberts on Sun, 15 Oct 2006 10:03:35 +1300) Subject: Re: [commit] gdb.texinfo Reply-to: Eli Zaretskii References: <17712.11682.59131.269703@kahikatea.snap.net.nz> <17713.20647.37355.257609@kahikatea.snap.net.nz> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00172.txt.bz2 > From: Nick Roberts > 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 * 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