On Feb 17, 2008 11:35 AM, Markus Schiltknecht <[EMAIL PROTECTED]> wrote: > Hm.. that's a point. But using mainly shared memory for inter process > communication, this won't help, because there's no (or only few) system > calling involved. So the scheduling might very well differ.
Regarding sharing memory between processes: record/replay techniques for multithreaded processes are well known and have been documented. The challenge with memory that is shared between processes is how to share the recorded event data between the processes. > I'm also unclear on how easy it would be to "construct" the wanted > situations. Especially if the underlying code changes, so that the > issued system calls suddenly don't match the recorded ones anymore. I'm not sure that it is possible to develop record/replay techniques when different binaries are involved during the record and the replay 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
