* gdb.texinfo (catch) [exception]: Document how to insert

        a breakpoint on user-defined exceptions when the exception
        name is identical to one of the language-defined ones.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 6d1c713887e42419251397ba49c8f28080f8fe71..4b757e0c04e5ba6f1f5d9ea6fb54d4176947b24e 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2008-10-01  Joel Brobecker  <brobecker@adacore.com>
+
+       * gdb.texinfo (catch) [exception]: Document how to insert
+       a breakpoint on user-defined exceptions when the exception
+       name is identical to one of the language-defined ones.
+
 2008-09-27  Tom Tromey  <tromey@redhat.com>
 
        * gdb.texinfo (Macros): Remove text about stringification,

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 9db0ff8a764f5c84ae302bcfda1ede34bbd2c7e9..dddc88b79e513c84574c9830c7d95d321a68b7a8 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -3614,6 +3614,15 @@ at the end of the command (eg @code{catch exception Program_Error}),
 the debugger will stop only when this specific exception is raised.
 Otherwise, the debugger stops execution when any Ada exception is raised.
 
+When inserting an exception catchpoint on a user-defined exception whose
+name is identical to one of the exceptions defined by the language, the
+fully qualified name must be used as the exception name.  Otherwise,
+@value{GDBN} will assume that it should stop on the pre-defined exception
+rather than the user-defined one.  For instance, assuming an exception
+called @code{Constraint_Error} is defined in package @code{Pck}, then
+the command to use to catch such exceptions is @kbd{catch exception
+Pck.Constraint_Error}.
+
 @item exception unhandled
 An exception that was raised but is not handled by the program.