This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[commit] Mention that rbreak can set breakpoints on all functions
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: gdb-patches at sources dot redhat dot com
- Date: Sat, 18 Sep 2004 15:32:18 +0300
- Subject: [commit] Mention that rbreak can set breakpoints on all functions
- References: <OF47A82493.236BBAC6-ON87256F10.005AAC5F-88256F10.005BF5C2@us.ibm.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Cc: bug-gdb-bounces+gilliam=us.ibm.com@gnu.org, gnu-gdb-bug@moderators.isc.org,
> Michael Chastain <mec.gnu@mindspring.com>, UHAP023@alpha1.rhbnc.ac.uk
> From: Paul Gilliam <gilliam@us.ibm.com>
> Date: Wed, 15 Sep 2004 09:44:24 -0700
>
> > I think "rbreak ." should do the trick.
>
> All most. It would be nice if it where possible to manage all those
> break-points together. One 'disable' for the whole bunch. Of course the
> user could "rbreak .", note the numbers of the first new breakpoint and
> the last, then use that range: "disable <n>-<m>" (is that right syntax?).
>
> Maybe what we want is to be able to name (automatically?) a range of
> breakpoints. Something like:
>
> gdb> rbreak .
> bp group "functionsBP" is 2-234
> gdb> disable functionsBP
> breakpoints 2-234 disabled
> gdb>
>
> Just a thought.
As the result of reading the thread Re: SET BREAK/CALL equiv. on gdb,
I committed the following patch to gdb.texinfo:
2004-09-16 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Set Breaks): Add index entry for setting
breakpoints on overloaded C++ functions that are not members of
any classes. Add an example and an index entry for setting
breakpoints on all program functions.
--- src/gdb/doc/gdb.texinfo 30 Jul 2004 19:23:54 -0000 1.212
+++ src/gdb/doc/gdb.texinfo 16 Sep 2004 11:15:24 -0000 1.213
@@ -2590,10 +2590,19 @@
@code{.*} leading and trailing the regular expression you supply, so to
match only functions that begin with @code{foo}, use @code{^foo}.
+@cindex non-member C@t{++} functions, set breakpoint in
When debugging C@t{++} programs, @code{rbreak} is useful for setting
breakpoints on overloaded functions that are not members of any special
classes.
+@cindex set breakpoints on all functions
+The @code{rbreak} command can be used to set breakpoints in
+@strong{all} the functions in a program, like this:
+
+@smallexample
+(@value{GDBP}) rbreak .
+@end smallexample
+