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 <mdw@distorted.org.uk>
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>

diff --git a/regress/r1test b/regress/r1test
index d981b450e0831428a353055177ad0bb1bde623b9..b2549e732378d3116c1785042c34f3c9b058dbfa 100755 (executable)
--- 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