[PATCH 1/6] gdb/unittests: catch gdb_exception_error in scoped_mmap test

[Simon Marchi <simon.marchi@efficios.com>]

Most places should generally catch gdb_exception_error and not
gdb_exception, to avoid catching gdb_exception_quit and
gdb_exception_forced_quit.  I think that this function is such a place.  I
happened to see it while working on a following patch.

While at it, format the try/catch block using the correct style.

Change-Id: I80e1d43d3ea2f940e3b75baae77672e267fde446
---
 gdb/unittests/scoped_mmap-selftests.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/gdb/unittests/scoped_mmap-selftests.c b/gdb/unittests/scoped_mmap-selftests.c
index 06026b459cda..ce03d7559f7a 100644
--- a/gdb/unittests/scoped_mmap-selftests.c
+++ b/gdb/unittests/scoped_mmap-selftests.c
@@ -112,11 +112,14 @@ test_invalid_filename ()
 {
   bool threw = false;
 
-  try {
+  try
+    {
       ::scoped_mmap m = ::mmap_file ("/this/file/should/not/exist");
-  } catch (const gdb_exception &e) {
+    }
+  catch (const gdb_exception_error &)
+    {
       threw = true;
-  }
+    }
 
   SELF_CHECK (threw);
 }
-- 
2.56.0