test: don't make timer offset errors fatal in gdb

No way we can debug without triggering those, so let's not make them fatal.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

diff --git a/test/litest.c b/test/litest.c
index 1230ec9..ab5a73a 100644 (file)
--- a/test/litest.c
+++ b/test/litest.c
@@ -648,7 +648,7 @@ litest_log_handler(struct libinput *libinput,
                /* valgrind is too slow and some of our offsets are too
                 * short, don't abort if during a valgrind run we get a
                 * negative offset */
-               if (!RUNNING_ON_VALGRIND ||
+               if ((!RUNNING_ON_VALGRIND && !in_debugger) ||
                    !strstr(format, "offset negative"))
                litest_abort_msg("libinput bug triggered, aborting.\n");
        }