Tim lawless wrote: >Further, system call interposition will be problematic for some >systemcalls. For example, execve(). This one is a >'they-check-in-but-don't-check-out' function. Why is this a problem? The 'execve() returned' event is not meaningful unless execve() failed. >Other, less problematic syscalls also exist -- vfork. Why is this any harder than fork() or clone()? In fact, vfork() seems to be a special case of clone(). I think that I am having trouble understanding your mental model. Are you and I making different assumptions here somehow?
This archive was generated by hypermail 2b30 : Fri Apr 13 2001 - 14:15:29 PDT