|
From: Diane M <dia...@gm...> - 2017-08-30 16:29:35
|
Ivo, On Aug 24, 2017, at 4:39 AM, Ivo Raisr <iv...@iv...> wrote: Dear Valgrind developers, I had just a thought if it would be possible for Valgrind/Memchek to instrument a binary just once, save the instrumented code in a pre-image and then execute it many times already instrumented. My motivation is a huge binary which takes a lot of time to instrument and which is executed frequently during many many test suite runs without any human intervention. What would be the major challenges here? My preliminary idea was that trans-cache could request blocks either from VEX or from the pre-image. So do you mean that valgrind would store translated blocks in a (memory-mapped) file and then search for them before translating and instrumenting? If so, this is interesting, but I suspect that it will not speed things up much. The search would have to be a lot faster than the disassembly plus instrument in order to make a big difference. If you are considering translating the entire program and caching it, I think that would be much faster, but probably not possible with the way that valgrind works. Diane On Thu, Aug 24, 2017 at 4:39 AM, Ivo Raisr <iv...@iv...> wrote: > Dear Valgrind developers, > > I had just a thought if it would be possible for Valgrind/Memchek to > instrument a binary just once, > save the instrumented code in a pre-image and then execute it many > times already instrumented. > > My motivation is a huge binary which takes a lot of time to instrument and > which > is executed frequently during many many test suite runs without any > human intervention. > > What would be the major challenges here? > My preliminary idea was that trans-cache could request blocks either > from VEX or from the pre-image. > > Please let me know your thoughts! > Thank you, > I. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |