|
From: Nicholas N. <nj...@ca...> - 2004-06-02 20:51:57
|
On Wed, 2 Jun 2004, Stephen McCamant wrote: > I thought you might be interested to hear about a Valgrind-based tool > our research group just released the first version of. Named Kvasir, Cool! Nice name :) > This first version is a bit roughly assembled, being based on the > Sparrow skin, parts of Memcheck, and the GNU Binutils "readelf" > program, assembled with some modifications essentially by cut and > paste (along with a slightly modified version of the Valgrind core, > circa 2.1.1) together with our own code. In the future, we'd like to > use resources from Valgrind in a more principled way, ideally making a > tool that could be dropped into an unmodified Valgrind > distribution. We expect there are only a few places in the rest of > Valgrind that would need to be more flexible to accommodate this (for > instance, we don't want Memcheck's V bits to be set to "valid" after > an invalid access). What changes to Valgrind's core would you require to make Kvasir a normal drop-in Valgrind tool? Sounds like improved debug info support is one. (Nb: I'm not promising anything with those sentences :) The V bits setting sounds like purely a tool/skin issue, though. N |