summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/valgrind.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/valgrind.mdwn')
-rw-r--r--community/gsoc/project_ideas/valgrind.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/valgrind.mdwn b/community/gsoc/project_ideas/valgrind.mdwn
index e9e94857..6663eec2 100644
--- a/community/gsoc/project_ideas/valgrind.mdwn
+++ b/community/gsoc/project_ideas/valgrind.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2009, 2010, 2011 Free Software Foundation,
+[[!meta copyright="Copyright © 2009, 2010, 2011, 2013 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -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.