|
From: Nicholas N. <nj...@cs...> - 2008-07-26 09:05:35
|
On Thu, 24 Jul 2008, MoJiong Qiu wrote: > I have spent some time implementing a prototype of record and replay in > the valgrind core based on intercepting and recording syscall results and > playing back their results. So far, I have only wrapped a dozen or so > syscalls and valgrind only records and replays small single threaded > programs. I am able to record execution for these small programs with > this modified valgrind core with no analysis, and have the core replay the > execution while turning on instrumentation and analysis (I turned on > cachegrind while replaying). More complex client programs can be > supported as more syscalls are recorded and replayed. It doesn't > currently support multithreading or signal delivery, though I expect > recording and replaying these should be doable as well. You say you record the system calls, but then you run Cachegrind on the replayed code. Are you running all the original instructions during the replay? Nick |