Re: [Valgrind-developers] Record/replay support in valgrind

[MoJiong Q. <qm...@ho...>]

> How general will your record/replay tool be ? Are you aware that not> only system calls but also I/O instructions like rdtsc, inb, outb,> inw, outw have to be recorded ? And the result of loads and stores to> memory-mapped address ranges will have to be recorded too.> 
Yes, all the things you mentioned are hard to be recorded. Besides, shared memory with other process is also a problem. These difficulities may limit the usages of syscall-based record/replay.
 
However, some of them could be solved since Valgrind takes full control of client program, I think. Sensitive instructions like rdtsc and I/O instructions could be specially treated and instrumented by Valgrind; Memory-mapped address ranges without MAP_SHARED flag could be wholly logged down and saved as a file for replay, though performance is an issue. But shared memory is a big problem.
 
Any comments or any suggestions are welcome. They will help me a lot:)
 
Thanks,
Mojiong
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx