From bf1abac9773a427f2e5aabfc91245f7c8d424fb5 Mon Sep 17 00:00:00 2001
From: Matthias Clasen <mclasen@redhat.com>
Date: Thu, 27 Aug 2020 14:11:09 -0400
Subject: [PATCH] ci: Use catchsegv catching stacktraces

Seems better than patching backtrace() calls into
our test binaries.
---
 .gitlab-ci/run-tests.sh | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.gitlab-ci/run-tests.sh b/.gitlab-ci/run-tests.sh
index 6f6a09258f..8a16ce4e60 100755
--- a/.gitlab-ci/run-tests.sh
+++ b/.gitlab-ci/run-tests.sh
@@ -17,6 +17,7 @@ case "${backend}" in
                 --timeout-multiplier "${MESON_TEST_TIMEOUT_MULTIPLIER}" \
                 --print-errorlogs \
                 --setup=${backend} \
+                --wrap catchsegv \
                 --suite=gtk \
                 --no-suite=gsk-compare-broadway
 
@@ -36,6 +37,7 @@ case "${backend}" in
                 --timeout-multiplier "${MESON_TEST_TIMEOUT_MULTIPLIER}" \
                 --print-errorlogs \
                 --setup=${backend} \
+                --wrap catchsegv \
                 --suite=gtk \
                 --no-suite=gsk-compare-broadway
 
@@ -54,6 +56,7 @@ case "${backend}" in
                 --timeout-multiplier "${MESON_TEST_TIMEOUT_MULTIPLIER}" \
                 --print-errorlogs \
                 --setup=${backend} \
+                --wrap catchsegv \
                 --suite=gtk \
                 --no-suite=gsk-compare-opengl