From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Sun, 30 Aug 2015 15:44:07 +0000 (+0000)
Subject: use verbosity 1 to report multiple termination of gdbserver,
X-Git-Tag: svn/VALGRIND_3_11_0~58
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3a4ce807551b0c223e7b0e1f419996df52537225;p=thirdparty%2Fvalgrind.git

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
---

diff --git a/coregrind/m_gdbserver/m_gdbserver.c b/coregrind/m_gdbserver/m_gdbserver.c
index a5e8083b09..d5cc8eae49 100644
--- a/coregrind/m_gdbserver/m_gdbserver.c
+++ b/coregrind/m_gdbserver/m_gdbserver.c
@@ -790,7 +790,7 @@ void VG_(gdbserver) ( ThreadId tid )
       if (gdbserver_called == 0) {
          dlog(1, "VG_(gdbserver) called to terminate, nothing to terminate\n");
       } else if (gdbserver_exited) {
-         dlog(0, "VG_(gdbserver) called to terminate again %d\n",
+         dlog(1, "VG_(gdbserver) called to terminate again %d\n",
               gdbserver_exited);
       } else {
          gdbserver_terminate();