|
From: Sérgio D. J. <ser...@li...> - 2008-10-11 22:06:34
|
Hi Bart, On Sat, 2008-10-11 at 21:40 +0200, Bart Van Assche wrote: > The above race report refers to stdout. glibc uses its own locking > mechanism for streams (see also _IO_flockfile(FILE*) in the glibc > source tree). Some of these races were already suppressed by drd, but > not all. This has been fixed (trunk, revision 8663). Thanks for > reporting this. Thanks. I've updated my local copy of the repository and am the tests again. I'll let you know if there's something strange happening. Meanwhile, I'd like to ask a question about the limitations of Valgrind when libgomp uses sys_futex() to make the barrier implementation. I've tried to investigate and understand more about this subject, but unfortunately it seems a little Valgrind-specific (and I'm still new on this field). I've found the following thread discussion involving you and Julian: http://www.mail-archive.com/val...@li.../msg02349.html So, could you explain a little more why do I have to recompile gcc using the --disable-linux-futex parameter? Best regards, -- Sérgio Durigan Júnior Linux on Power Toolchain - Software Engineer Linux Technology Center - LTC IBM Brazil |