[Spice-devel] [PATCH v2] tests: exit on SIGABRT
Frediano Ziglio
fziglio at redhat.com
Thu Jan 28 07:00:29 PST 2016
Fatal error exit usually with abort() causing SIGABRT to be triggered
which can have problems with core dump generation depending on system
settings. Capturing and exiting on this signal solve the problem.
Signed-off-by: Frediano Ziglio <fziglio at redhat.com>
---
tests/test-logging.c | 6 ++++++
1 file changed, 6 insertions(+)
Changes from v1:
- fix typo in commit message.
diff --git a/tests/test-logging.c b/tests/test-logging.c
index 008ce48..dad7a60 100644
--- a/tests/test-logging.c
+++ b/tests/test-logging.c
@@ -376,11 +376,17 @@ static void test_spice_g_messages_debug_all(void)
g_test_trap_assert_stderr("*g_message\n*other_message\n");
}
+static void handle_sigabrt(int sig)
+{
+ _exit(1);
+}
int main(int argc, char **argv)
{
GLogLevelFlags fatal_mask;
+ signal(SIGABRT, handle_sigabrt);
+
fatal_mask = (GLogLevelFlags)g_log_set_always_fatal((GLogLevelFlags) G_LOG_FATAL_MASK);
g_test_init(&argc, &argv, NULL);
--
2.4.3
More information about the Spice-devel
mailing list