I have an oracle who tells me that the child side of a particular clone() should not be monitored: valgrind should "let go" of the child (whether thread or fork) as soon as possible. Waiting for execve(), to let go as in "--trace-children=no", is not an option. What is a good way for valgrind let go relatively immediately?
It looks like one option is to have a of ThreadState.exitReason of VgSrc_LetGo that behaves almost the same as VgSrc_ExitSyscall. But rather than calling sys_exit(), instead VgSrc_LetGo re-establishes the usercode signal handlers, then the usercode registers, and finally the usercode instruction pointer. Comments? -- John Reiser, [EMAIL PROTECTED] ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
