Re: [Valgrind-users] helgrind and double checked initialization

2011-08-28 Thread Bart Van Assche
On Sun, Aug 28, 2011 at 5:44 AM, Jeffrey Walton noloa...@gmail.com wrote: I want to use double checked initialization for a program, but I'm catching some warnings from helgrind. A typical use is shown below. Its kind of tedious to run --gen-suppressions=yes for to develop suppressions. Plus,

Re: [Valgrind-users] helgrind and double checked initialization

2011-08-28 Thread Bart Van Assche
On Sun, Aug 28, 2011 at 2:32 PM, Milian Wolff m...@milianw.de wrote: On Saturday 27 August 2011 23:44:02 Jeffrey Walton wrote: I want to use double checked initialization for a program, but I'm catching some warnings from helgrind. A typical use is shown below. Its kind of tedious to run

Re: [Valgrind-users] helgrind and double checked initialization

2011-08-28 Thread Jeffrey Walton
Thanks Bart, On Sun, Aug 28, 2011 at 12:26 PM, Bart Van Assche bvanass...@acm.org wrote: On Sun, Aug 28, 2011 at 6:13 PM, Jeffrey Walton noloa...@gmail.com wrote: (1) Never trust wikipedia. Reading your message makes me wonder whether you are familiar with the reason why memory barriers

Re: [Valgrind-users] helgrind and double checked initialization

2011-08-28 Thread Bart Van Assche
On Sun, Aug 28, 2011 at 6:55 PM, Jeffrey Walton noloa...@gmail.com wrote: On Sun, Aug 28, 2011 at 12:26 PM, Bart Van Assche bvanass...@acm.org wrote: On Sun, Aug 28, 2011 at 6:13 PM, Jeffrey Walton noloa...@gmail.com wrote: (1) Never trust wikipedia. Reading your message makes me wonder

[Valgrind-users] Possible data race: mythread_wrapper (hg_intercepts.c:199)

2011-08-28 Thread Jeffrey Walton
Hi All, Is it safe to ignore warnings from mythread_wrapper? The test program causing the warning spins up 64 threads and exercises the SecureRandom. Jeff ==27224== Thread #2 was created ==27224==at 0x32EF2E0BEE: clone (in /lib64/libc-2.13.so) ==27224==by 0x32EFA05D9F: do_clone.clone.2