|
From: Dennis L. <pla...@in...> - 2005-07-19 17:12:19
|
At 18:47 19.07.2005, Nicholas Nethercote wrote: >On Tue, 19 Jul 2005, Duncan Sands wrote: > >Jeremy wrote some code to intercept pthread functions, which would allow >Helgrind to be reinstated. It's currently commented out in the 3.0 >version, and I'm not sure how well it was working. > >Helgrind doesn't seem very popular in general. The December 2003 survey >told us that it accounted for less than 1% of all Valgrind use, and the >feedback since then hasn't given me any indication that things have changed. > >Nonetheless, we would like to get Helgrind working again. The >pthread-interception stuff is also necessary to get the basic pthread >error checking working again. I personally used helgrind in the "old days" quite often. Although it gave tons of (more or less) false positives (sometimes program flow does prevent concurrent access which cant be detected by helgrind of course) it was really very useful and I found many bugs. I check rather often if something is done at the helgrind front since there is no similar free tool. I think a big problem why not many people use helgrind is because they know valgrind as "memory overflow, leak check and uninitialized value detection tool" but not as the powerful framework for many other tools (massif is of great use sometimes too) that it actually is. Perhaps more advertising other feature tools of valgrind will increase knowledge and thus usage too. Perhaps the next survey should include (if the old didnt already) a "have you heard about tool xxx previously" question before asking fo its usage... greets Dennis Carpe quod tibi datum est |