From: Magnus Reftel <magnus.reftel@gm...> - 2013-06-19 09:24:30
in a unit testing harness, we have a lock that ensures that only one thread
runs at a time. In production, there is no such global lock, but instead our
code tries to protects its own data using various mutexes etc. We run our test
suite under Helgrind, but it seems like the global lock we have for testing
purposes causes false negatives as it prevents Helgrind from detecting data
races that could show up in production, since all threads in all testcases
always have at lest the global test harness lock held.
Is there a way to tell Helgrind to disregard that particular lock when
analyzing data races?