aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2013-04-15 17:20:39 +0000
committerTom Tromey <tromey@redhat.com>2013-04-15 17:20:39 +0000
commit02ae6bada6a291c3b71ceea392be196d768d86a4 (patch)
treecf59863c57ccab169fcd3e3958a07d5a91d0a687 /gdb
parente79c84aa33d03bd43404565f5b98c78a8f98ab95 (diff)
downloadgdb-02ae6bada6a291c3b71ceea392be196d768d86a4.zip
gdb-02ae6bada6a291c3b71ceea392be196d768d86a4.tar.gz
gdb-02ae6bada6a291c3b71ceea392be196d768d86a4.tar.bz2
* gdb.texinfo (Set Catchpoints): Remove obsolete text.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/ChangeLog4
-rw-r--r--gdb/doc/gdb.texinfo30
2 files changed, 4 insertions, 30 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index faa0d50..023d44b 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2013-04-15 Tom Tromey <tromey@redhat.com>
+
+ * gdb.texinfo (Set Catchpoints): Remove obsolete text.
+
2013-04-12 Jan Kratochvil <jan.kratochvil@redhat.com>
Eli Zaretskii <eliz@gnu.org>
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 01e20d6..f802116 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4309,36 +4309,6 @@ You cannot raise an exception interactively.
You cannot install an exception handler interactively.
@end itemize
-@cindex raise exceptions
-Sometimes @code{catch} is not the best way to debug exception handling:
-if you need to know exactly where an exception is raised, it is better to
-stop @emph{before} the exception handler is called, since that way you
-can see the stack before any unwinding takes place. If you set a
-breakpoint in an exception handler instead, it may not be easy to find
-out where the exception was raised.
-
-To stop just before an exception handler is called, you need some
-knowledge of the implementation. In the case of @sc{gnu} C@t{++}, exceptions are
-raised by calling a library function named @code{__raise_exception}
-which has the following ANSI C interface:
-
-@smallexample
- /* @var{addr} is where the exception identifier is stored.
- @var{id} is the exception identifier. */
- void __raise_exception (void **addr, void *id);
-@end smallexample
-
-@noindent
-To make the debugger catch all exceptions before any stack
-unwinding takes place, set a breakpoint on @code{__raise_exception}
-(@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Exceptions}).
-
-With a conditional breakpoint (@pxref{Conditions, ,Break Conditions})
-that depends on the value of @var{id}, you can stop your program when
-a specific exception is raised. You can use multiple conditional
-breakpoints to stop your program when any of a number of exceptions are
-raised.
-
@node Delete Breaks
@subsection Deleting Breakpoints