Julian Seward wrote: Hi Julian,
>> I am willing to test a bunch of shell utilities and code to find more >> syscalls that are missing, but should I open individual tickets for each >> syscall or stuff them onto the existing ticket? > > Put them all on the existing ticket. The important information is, in > each case, the syscall number and the architecture (x86, amd64, etc). Ok, will do. > Actually if you look at the function setup_post_syscall_table in h_main.c > it's easy to add the missing entries. Adding _NR_getursage to that table fixes the issue I observed, I haven't tried the other syscall yet. > Syscalls which don't return > pointers (almost all syscalls) can just be added to the table without > any further thought. (The important distinction here is: does this > syscall return a pointer, or a non-pointer) ? Excellent to know - at least something I can contribute patches for as valgrind n00b coder :) I assume syscalls that return pointers are somewhat more difficult to deal with? > J > Cheers, Michael ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
