|
From: Arndt M. <amu...@is...> - 2005-07-20 13:41:30
|
Nicholas Nethercote wrote: > On Tue, 19 Jul 2005, Julian Seward wrote: > >> I must say I find helgrind perplexing and frustrating, because it's >> potentially such an incredibly useful tool, yet we have never really >> made it work as convincingly as I'd like, and now we seem to be >> slipping away from being able to support it. I'd love to be able to >> make a good showing with Helgrind in the future, but it strikes me >> that the difficulties with it put it right at the edge of the >> state-of-the-art. > > > I think data race detection is definitely not a solved problem. As > Arndt pointed out, being able to use Valgrind/Helgrind as a platform > for research in this area is a worthy goal. That's the point, indeed. How much work is it to make Helgrind work in 3.0 again? (Roughly) I would like to volunteer if it's not too difficult and I get some help. Anyway, it would be good for me to understand Valgrind and Helgrind, because afterwards it would be easier to experiment with this platform. I suppose on-the-fly methods are the only practical ways to hunt for concurrent bugs, I found static or model checking techniques impractical for most real-world and large applications. Concerning the performance issues: Did you try to implement a logging mechanism that lets you do the analyses offline? Although, in most cases the amount of data that has to be stored would be too much, but sometimes it might be a useful feature. Arndt |