commit 69a72a5fd2a6ba3a54d7c74117d3a97609d4fd91
author sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Sun Nov 03 13:41:41 2002 +0000
committer sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Sun Nov 03 13:41:41 2002 +0000
tree 1aaaa9613e5a6fbfe1af87f68ea827642cf2f658
parent 570f8907c6da52a0e61cac5aa1d0507b3b7c8aad

Add a new client request, VG_USERREQ__LOGMESSAGE, and use this to route
all commentary from our libpthread.so through to the valgrind core and
hence to the selected logging sink.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1274 a5019735-40e9-0310-863c-91ae7b9d1cf9

coregrind/vg_scheduler.c

diff --git a/coregrind/vg_scheduler.c b/coregrind/vg_scheduler.c
index 59804c4..0226d46 100644
--- a/coregrind/vg_scheduler.c
+++ b/coregrind/vg_scheduler.c
@@ -3469,6 +3469,10 @@
       case VG_USERREQ__SIGNAL_RETURNS: 
          handle_signal_return(tid);
 	 break;
+ 
+      case VG_USERREQ__LOGMESSAGE:
+         VG_(message)(Vg_UserMsg, "%s", (Char*)(arg[1]));
+         break;
 
       /* Requests from the client program */