[Valgrind-developers] valgrind: r5478 - branches/VALGRIND_3_1_BRANCH/coregrind

[<sv...@va...>]

Author: dirk
Date: 2006-01-02 19:34:53 +0000 (Mon, 02 Jan 2006)
New Revision: 5478

Log:
backport from trunk:
r5325 | njn | 2005-12-12 16:54:50 +0100 (Mon, 12 Dec 2005) | 3 lines

Make it clearer that internal errors are Valgrind's fault.

Modified:
   branches/VALGRIND_3_1_BRANCH/coregrind/m_signals.c


Modified: branches/VALGRIND_3_1_BRANCH/coregrind/m_signals.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- branches/VALGRIND_3_1_BRANCH/coregrind/m_signals.c	2006-01-02 19:06:3=
7 UTC (rev 5477)
+++ branches/VALGRIND_3_1_BRANCH/coregrind/m_signals.c	2006-01-02 19:34:5=
3 UTC (rev 5478)
@@ -1699,7 +1699,7 @@
 	 Valgrind internally.
        */
       VG_(message)(Vg_DebugMsg,=20
-		   "INTERNAL ERROR: Valgrind received a signal %d (%s) - exiting",
+		   "VALGRIND INTERNAL ERROR: Valgrind received a signal %d (%s) - exit=
ing",
 		   sigNo, signame(sigNo));
=20
       VG_(message)(Vg_DebugMsg,=20