From 0842d28f339ff95883a37638102bf58026a3c88c Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sun, 25 Aug 2013 14:48:21 +0200 Subject: mention rpctrace, as Justus Winter suggested --- community/gsoc/project_ideas/valgrind.mdwn | 2 ++ 1 file changed, 2 insertions(+) (limited to 'community/gsoc/project_ideas') diff --git a/community/gsoc/project_ideas/valgrind.mdwn b/community/gsoc/project_ideas/valgrind.mdwn index e9e94857..76675796 100644 --- a/community/gsoc/project_ideas/valgrind.mdwn +++ b/community/gsoc/project_ideas/valgrind.mdwn @@ -60,6 +60,8 @@ Such specific semantics can't be deduced from the message headers alone. Thus for a complete port, it will still be necessary to go through the list of all known RPCs, and implement special handling in Valgrind for those RPCs that need it. +Reading the source code of the rpctrace tool would probably be useful to +understand how the RPC message can be parsed. The goal of this task is at minimum to make Valgrind grok Mach traps, and to implement the generic RPC handler. -- cgit v1.2.3