From 7d01629580949a18960f79603fca1d0edb337aa1 Mon Sep 17 00:00:00 2001 From: Gerion Entrup Date: Wed, 2 Oct 2019 14:51:02 +0200 Subject: mtest: add gdb_path option When using the '--gdb' argument of meson test the executed binary can now be specified with '--gdb-path'. Closing: #4373 --- docs/markdown/Unit-tests.md | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/markdown/Unit-tests.md') diff --git a/docs/markdown/Unit-tests.md b/docs/markdown/Unit-tests.md index 9c2e3d50b..c89d7b043 100644 --- a/docs/markdown/Unit-tests.md +++ b/docs/markdown/Unit-tests.md @@ -157,6 +157,12 @@ $ meson test --gdb --repeat=10000 testname This runs the test up to 10 000 times under GDB automatically. If the program crashes, GDB will halt and the user can debug the application. Note that testing timeouts are disabled in this case so `meson test` will not kill `gdb` while the developer is still debugging it. The downside is that if the test binary freezes, the test runner will wait forever. +Sometimes, the GDB binary is not in the PATH variable or the user wants to use a GDB replacement. Therefore, the invoked GDB program can be specified *(added 0.52.0)*: + +```console +$ meson test --gdb --gdb-path /path/to/gdb testname +``` + ```console $ meson test --print-errorlogs ``` -- cgit v1.2.3