[NEWS] Document condition at end of catch exception/assert commands

gdb/ChangeLog:

        * NEWS: Document the fact that one can provide a condition when
        creating an Ada exception catchpoint.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 3db8b8d2d28d12e4efa94b6d75c0bdf72941349e..48ebb4b33995199810820cb3c49d383e904b8748 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2012-03-01  Joel Brobecker  <brobecker@adacore.com>
+
+       * NEWS: Document the fact that one can provide a condition when
+       creating an Ada exception catchpoint.
+
 2012-03-01  Tom Tromey  <tromey@redhat.com>
 
        * valprint.c (val_print_type_code_flags): Fix placement of

diff --git a/gdb/NEWS b/gdb/NEWS
index 090a065fe2a21bb394ade6f1c5da45b405caaea5..7a4812b662862874011b1fa59014d5533814db86 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -44,6 +44,16 @@
 * The command "info catch" has been removed.  It has been disabled
   since December 2007.
 
+* The "catch exception" and "catch assert" commands now accept
+  a condition at the end of the command, much like the "break"
+  command does. For instance:
+
+        (gdb) catch exception Constraint_Error if Barrier = True
+
+  Previously, it was possible to add a condition to such catchpoints,
+  but it had to be done as a second step, after the catchpoint had been
+  created, using the "condition" command.
+
 * New commands
 
   ** "catch load" and "catch unload" can be used to stop when a shared