From ea5b764eb48f770c67b9e1a8eaa7113e3ac28915 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Mon, 17 Jun 2019 11:35:31 +1000 Subject: [PATCH] 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 --- test/litest.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/litest.c b/test/litest.c index 1230ec93..ab5a73a5 100644 --- 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"); }