diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-08-25 14:48:21 +0200 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-08-25 14:48:21 +0200 |
| commit | 0842d28f339ff95883a37638102bf58026a3c88c (patch) | |
| tree | ac002ef6d05cc94827faf57b3cba7e5325e8c8d1 /community/gsoc | |
| parent | eab9d259411d67cc9a9d1e4d81c23a04dfd67b51 (diff) | |
mention rpctrace, as Justus Winter suggested
Diffstat (limited to 'community/gsoc')
| -rw-r--r-- | community/gsoc/project_ideas/valgrind.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
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. |