On Feb 17, 2008 11:05 AM, Markus Schiltknecht <[EMAIL PROTECTED]> wrote: > However, what bugs me more is, that there would need to be an interface > to valgrind, to control the internal scheduler (to be able to start and > stop threads or processes based on some external events).
I think that it is possible to implement a record/replay tool for multiple processes without modifying the Valgrind scheduler. During the recording phase you can gather information about any event that influences interprocess ordering by intercepting system calls like recv(), send(), sendto(), kill(), ... During the replay phase you can intercept the same system calls and delay their execution in such a way that scheduling during replay matches scheduling during the recording phase. Bart. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
