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:
$ 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>
set +e
ADNS_TEST_REPORT_FD=3 ADNS_TEST_IN_FD=4 \
3>>"$ocase.report" 4<&4 >"$ocase.out" 2>"$ocase.err" \
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
+ $debug $playback $initflags"$initstring" $queryargs