summaryrefslogtreecommitdiff
path: root/libevdev
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2013-12-24 08:19:16 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2013-12-24 09:14:12 +1000
commitfd3118ea1ac1442e5bf960e3d577aacc08aa3d63 (patch)
treefdb7f5b533cda98203c3c52743b2593920c807b2 /libevdev
parent49f0b9300e394889e2dd3964fe29e493265f1683 (diff)
downloadlibevdev-fd3118ea1ac1442e5bf960e3d577aacc08aa3d63.tar.gz
test: detect if we're running inside gdb and disable forking
The Check test framework forks by default which is annoying when running gdb. Try to detect whether we're inside gdb by ptracing ourselves. If that works, we're not inside a debugger. If it doesn't, then assume we're inside a debugger and set CK_FORK to "no". Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'libevdev')
-rw-r--r--libevdev/libevdev.h5
1 files changed, 3 insertions, 2 deletions
diff --git a/libevdev/libevdev.h b/libevdev/libevdev.h
index 37ca2f4..f5ceda0 100644
--- a/libevdev/libevdev.h
+++ b/libevdev/libevdev.h
@@ -177,8 +177,9 @@ extern "C" {
* git grep "suite_create"
* git grep "tcase_create"
*
- * By default, check forks, making debugging harder. Run gdb as below to avoid
- * forking.
+ * By default, Check forks, making debugging harder. The test suite tries to detect
+ * if it is running inside gdb and disable forking. If that doesn't work for
+ * some reason, run gdb as below to avoid forking.
*
* sudo CK_FORK=no CK_RUN_TEST="test case name" gdb ./test/test-libevdev
*