* 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.
This commit is contained in:
Joel Brobecker
2008-10-01 16:44:47 +00:00
parent b887350fc5
commit 87f67dbac2
2 changed files with 15 additions and 0 deletions

View File

@ -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> 2008-09-27 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Macros): Remove text about stringification, * gdb.texinfo (Macros): Remove text about stringification,

View File

@ -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. the debugger will stop only when this specific exception is raised.
Otherwise, the debugger stops execution when any Ada 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 @item exception unhandled
An exception that was raised but is not handled by the program. An exception that was raised but is not handled by the program.