On Mon, 16 Jan 2012 10:48:28 +0100, Frederick Roth wrote:
On Thu, 12 Jan 2012 03:13:38 -0800 (PST), Vicente Botet wrote:
Frederick Roth wrote
On Thu, 05 Jan 2012 09:04:46 +0100, Frederick Roth wrote:
On Wed, 04 Jan 2012 22:01:01 +0100, Vicente J. Botet Escriba wrote:
Le 04/01/12 09:46, Frederick Roth a écrit :
I am currently fooling around with boost::thread. After writing a short example program (featuring boost::thread and boost::interprocess::interprocess_semaphore), I ran helgrind against it and got some "Possible data race" errors.
Hi, I missed you last post.
Anyway, the trace "Possible data race during read of size 4 at 0x46c6d32c by thread #3" doesn't help me too much. Is there any way helring can give the c++ variable names?
I got it to show the line-numbers in the boost library (once.hpp and once.cpp) i give you the output below. I hope it helps.
I did some googling and found the following boost trac entry which sounds similar to this. https://svn.boost.org/trac/boost/ticket/3526 The last comment states: "although every read of current_thread_tls_key happens after its initialization, this ordering is invisible to data race detection tools. That's why DRD complains about it. A suppression pattern for this access pattern will be added in Valgrind 3.6.0. " I did compile and test the main.cpp from the trac issue and valgrind-3.6.1 still reports the data race. I therefore assume, that the suppression pattern did not get into valgrind 3.6.0. -- Ich entschuldige mich nicht für Kunst!