use verbosity 1 to report multiple termination of gdbserver,
this can happen e.g. in case of irrecoverable execve failure.
This log was making tests fail randomly: the double termination
can only occur if gdbsrv was initialised.
After fork, gdbsrv is initialised by the next scheduler gdbsrv
activity check (by default, every 5000 blocks).
As a double termination has no effect, switch the trace to level 1.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15599 a5019735-40e9-0310-863c-91ae7b9d1cf9
1 file changed