* [commit] gdb.texinfo
@ 2006-10-14 0:24 Nick Roberts
2006-10-14 18:35 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Nick Roberts @ 2006-10-14 0:24 UTC (permalink / raw)
To: gdb-patches
This tidies up an earlier change that I made. Committed as obvious.
--
Nick http://www.inet.net.nz/~nickrob
2006-10-14 Nick Roberts <nickrob@snap.net.nz>
* gdb.texinfo (Backtrace): Order correctly and add other cases.
*** /home/nickrob/src/gdb/doc/gdb.texinfo.~1.356~ 2006-10-14 13:16:41.000000000 +1300
--- /home/nickrob/src/gdb/doc/gdb.texinfo 2006-10-14 13:14:49.000000000 +1300
***************
*** 4466,4473 ****
Similar, but print only the outermost @var{n} frames.
@item backtrace full
- Print the values of the local variables also.
@itemx bt full
@end table
@kindex where
--- 4466,4475 ----
Similar, but print only the outermost @var{n} frames.
@item backtrace full
@itemx bt full
+ @itemx bt full @var{n}
+ @itemx bt full -@var{n}
+ Print the values of the local variables also.
@end table
@kindex where
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [commit] gdb.texinfo
2006-10-14 0:24 [commit] gdb.texinfo Nick Roberts
@ 2006-10-14 18:35 ` Eli Zaretskii
2006-10-14 21:06 ` Nick Roberts
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2006-10-14 18:35 UTC (permalink / raw)
To: Nick Roberts; +Cc: gdb-patches
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 14 Oct 2006 13:21:54 +1300
>
> This tidies up an earlier change that I made. Committed as obvious.
Thanks. I applied a minor fix as shown:
2006-10-14 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Backtrace): Fix last change.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.357
retrieving revision 1.358
diff -u -r1.357 -r1.358
--- gdb.texinfo 14 Oct 2006 00:21:13 -0000 1.357
+++ gdb.texinfo 14 Oct 2006 18:34:02 -0000 1.358
@@ -4469,7 +4469,8 @@
@itemx bt full
@itemx bt full @var{n}
@itemx bt full -@var{n}
-Print the values of the local variables also.
+Print the values of the local variables also. @var{n} specifies the
+number of frames to print, like described above.
@end table
@kindex where
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [commit] gdb.texinfo
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
0 siblings, 2 replies; 6+ messages in thread
From: Nick Roberts @ 2006-10-14 21:06 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: gdb-patches
> Thanks. I applied a minor fix as shown:
>...
There are many similar discrepancies in the manual
`info signals'
`info handle'
should be:
`info signals [N]'
`info handle [N]'
`handle SIGNAL KEYWORDS...'
should be:
`handle SIGNAL [KEYWORDS...]'
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
info breakpoints [N]
doesn't describe what [N] does...
--
Nick http://www.inet.net.nz/~nickrob
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [commit] gdb.texinfo
2006-10-14 21:06 ` Nick Roberts
@ 2006-10-15 4:34 ` Eli Zaretskii
2006-10-15 21:36 ` Eli Zaretskii
1 sibling, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2006-10-15 4:34 UTC (permalink / raw)
To: Nick Roberts; +Cc: gdb-patches
> 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
Yep.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [commit] gdb.texinfo
2006-10-14 21:06 ` Nick Roberts
2006-10-15 4:34 ` Eli Zaretskii
@ 2006-10-15 21:36 ` Eli Zaretskii
2006-10-15 21:51 ` Nick Roberts
1 sibling, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2006-10-15 21:36 UTC (permalink / raw)
To: Nick Roberts; +Cc: gdb-patches
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [commit] gdb.texinfo
2006-10-15 21:36 ` Eli Zaretskii
@ 2006-10-15 21:51 ` Nick Roberts
0 siblings, 0 replies; 6+ messages in thread
From: Nick Roberts @ 2006-10-15 21:51 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: gdb-patches
>...
> Fixed.
Thanks.
> > 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''?
AFAICS `handle N' on it's own is the same as 'info handle N' and just prints
information about the specified signal.
--
Nick http://www.inet.net.nz/~nickrob
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-10-15 21:51 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-14 0:24 [commit] gdb.texinfo 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
2006-10-15 21:51 ` Nick Roberts
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox