> > 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?
Syscalls that return pointers are indeed a bit more tricky, but they are also very rare (eg, mmap) and I don't think you are likely to encounter any. The ideal is that you add entries to setup_post_syscall_table() so as to make it work for you, and then send us the patch (attach it to the bugzilla entry). Thanks, J ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
