|
From: John R.
|
>> The most likely way to implement such a feature in valgrind >> would be to have a Solaris-specific implementation of every system call >> that is affected by the special control word. If <stdlib.h> "read()" >> were affected then there would be a Solaris-specific version of >> "Int VG_(read)" [currently in coregrind/m_libcfile.c] which would >> implement the feature: test the word, call sigprocmask() if necessary, >> etc. That's the more subtle side, the one for valgrind internal uses. The obvious side is the stuff in coregrind/m_syswrap/priv_syswrap-generic.h and so on, which handles tracking the effects of system calls from emulated user code. |