From 1da660afaf3056f246215e52be47db4fc25103ba Mon Sep 17 00:00:00 2001 From: Mark Wooding Date: Sat, 31 May 2014 23:05:19 +0100 Subject: [PATCH] regress/r1test: Support an `ADNS_TEST_DEBUG' env var. Amazingly, sometimes the tests don't pass. When that happens, it's handy to be able to debug the library and find out why. It's a little tricky to attach GDB to the running process directly. I used the following: $ ADNS_TEST_DEBUG"noip gdbserver localhost:666" ./r1test CASE and then, in another terminal, something like $ noip gdb adnstest_s (gdb) target remote localhost:666 to debug the program. Signed-off-by: Mark Wooding Signed-off-by: Ian Jackson --- regress/r1test | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/regress/r1test b/regress/r1test index d981b45..b2549e7 100755 --- a/regress/r1test +++ b/regress/r1test @@ -67,7 +67,7 @@ fi set +e ADNS_TEST_REPORT_FD=3 ADNS_TEST_IN_FD=4 \ 3>>"$ocase.report" 4<&4 >"$ocase.out" 2>"$ocase.err" \ - $playback $initflags"$initstring" $queryargs + $ADNS_TEST_DEBUG $playback $initflags"$initstring" $queryargs rc=$? set -e -- 2.30.2