|
From: John v. S. <jc...@cs...> - 2007-05-21 13:11:10
|
Hello guys (the developers in particular), By coincidence, I stumbled on the recent paper of Nick and Julian (Valgrind: A Framework for Heavyweight Dynamic Binary Instrumentation, June 2007, PLDI'07). The paper is a great read and gives good in depth information about the valgrind implementation. But, there is always a but, as I'm writing a paper about valgrind myself for an experimentation project, I found out that a lot of things I described about valgrind were out of date (e.g. the loader/stage2 loading of valgrind, the handling of threads). So I'm about to rewrite a lot of stuff ;) But to avoid this in the future, what should be the best way to keep up to date with the changes in valgrind? Is there a road map of some kind? I _do_ read the valgrind development list, should that be sufficient? Cheers, John |
|
From: Nicholas N. <nj...@cs...> - 2007-05-21 22:25:00
|
On Mon, 21 May 2007, John van Schie wrote: > But, there is always a but, as I'm writing a paper about valgrind myself > for an experimentation project, I found out that a lot of things I > described about valgrind were out of date (e.g. the loader/stage2 > loading of valgrind, the handling of threads). > > So I'm about to rewrite a lot of stuff ;) But to avoid this in the > future, what should be the best way to keep up to date with the changes > in valgrind? Is there a road map of some kind? > I _do_ read the valgrind development list, should that be sufficient? The docs/internals/roadmap.txt file gives a rough overview, but there's not that much in there. You should always look at the one in the repository to ensure it's up to date. Apart from that, reading the dev list is the best thing. The good news is that Valgrind's internal architecture is more stable these days than in the past, so hopefully big changes will be rare. Nick |