From kde-bugs-dist Wed Oct 10 13:43:08 2007 From: Michael Lacher Date: Wed, 10 Oct 2007 13:43:08 +0000 To: kde-bugs-dist Subject: [Bug 137396] I would really like helgrind to work again... Message-Id: <20071010134308.9686.qmail () ktown ! kde ! org> X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=119202379924713 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. http://bugs.kde.org/show_bug.cgi?id=137396 ------- Additional Comments From mucki hlw co at 2007-10-10 15:43 ------- Julian Seward wrote: [bugs.kde.org quoted mail] No worries :) I am happy already to see that something is working and that valgrind is not really dead (the news section looks very quiet ;-) ) >> Which leads me to the question: what kinds of synchronization points are >> handled correctly. [...] >> detected ? It obviously works for mutexes, but would it work for example >> for a condition variable, a sempahore or memory barrier ? > > > Mutexes and condition variables. However it might be possible to extend it. > One way you could help is to send some small example programs using semaphores > and memory barriers, that demonstrate the problem. Then I can consider if > it is possible to fix the tool to handle them. > I'm, pretty swamped with work atm, and all my synchronization and threading stuff is buried in utility libs, so it might take a while, but I will see what I can do. It might take a while however.