[PATCH v5 2/6] [gdb/python] Make python selftest more robust

[Tom de Vries <tdevries@suse.de>]

When running the python selftest, we call raise directly:
...
    scoped_restore save_hook
      = make_scoped_restore (&hook_set_active_ext_lang,
			     []() { raise (SIGINT); });
...

While this tests the signal handling in its natural form, it runs the risk of
interference from other signals.

Instead:
- use signal_handler_selftest to isolate the selftest from user signals, and
- use "handle_sigint (SIGINT)" to deliver the signal.

Tested on x86_64-linux.
---
 gdb/python/python.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/gdb/python/python.c b/gdb/python/python.c
index d569fb5a3e4..00e8968d3ed 100644
--- a/gdb/python/python.c
+++ b/gdb/python/python.c
@@ -39,6 +39,7 @@
 
 #if GDB_SELF_TEST
 #include "gdbsupport/selftest.h"
+#include "event-top.h"
 #endif
 
 /* Declared constants and enum for python stack printing.  */
@@ -2246,11 +2247,15 @@ test_python ()
     SELF_CHECK (output.empty ());
   }
 
+  signal_handler_selftest a_signal_handler_selftest;
+  if (!a_signal_handler_selftest.valid ())
+    return;
+
   saw_exception = false;
   {
     scoped_restore save_hook
       = make_scoped_restore (&hook_set_active_ext_lang,
-			     []() { raise (SIGINT); });
+			     []() { handle_sigint (SIGINT); });
     try
       {
 	CMD (output);
-- 
2.35.3