I just tried valgrinding 7.4-cvs (compiled with valgrind support) on x86_x64 and get the following warnings when starting hilfe:

myst:7.4 $ ./bin/pike --valgrind=-q ==19948== Use of uninitialised value of size 8 ==19948== at 0x50168E: sub_node (las.c:439) ==19948== by 0x501881: debug_free_node (las.c:708) ==19948== by 0x50D152: dooptcode (las.c:5723) ==19948== by 0x422BC5: yyparse (language.yacc:864) ==19948== by 0x4D790E: run_pass2 (program.c:5864) ==19948== by 0x4D7C6D: compile (program.c:6081) ==19948== by 0x516F55: f_compile (builtin_functions.c:3331) ==19948== by 0x4ACBC0: get_master (object.c:552) ==19948== by 0x4ACE48: debug_master (object.c:598) ==19948== by 0x49E9DC: main (main.c:733) [repeated many times] --19948-- WARNING: unhandled syscall: 138 --19948-- You may be able to write your own handler. --19948-- Read the file README_MISSING_SYSCALL_OR_IOCTL. [repeated many times]

Anyone that can determine if the first is a valid error or not? The second warning appears to be setfsuid() which is rather uninteresting from a memory validity standpoint.