|
From: Sérgio D. J. <ser...@li...> - 2008-10-11 22:13:31
|
Hello Julian, On Sat, 2008-10-11 at 11:33 +0200, Julian Seward wrote: > Another thing you might want to do is try the "YARD" branch Helgrind > with those files. It has a lower false error rate and better error > messages than the trunk or 3.3.1 Helgrind, in that it shows you > tracebacks for both memory accesses involved in a race. It may also > behave better on ppc (maybe; am not sure about that). > > svn co svn://svn.valgrind.org/valgrind/branches/YARD yard > cd yard > ./autogen.sh > > then configure/build as usual. Well, I'll try that branch as well. But IMHO the main "problem" with both Helgrind and DRD is that you have to recompile GCC in order to get things working. That's why I want to understand what's currently "wrong" with GCC and OpenMP nowadays (specially regarding the sys_futex() syscall), and what can be done to get Helgrind/DRD working with default GCC versions that are usually shipped today. I've already sent an e-mail to Bart asking more details about this issue. > > By the way, is there an IRC channel or something where I can get in > > touch with you, guys? I've tried #valgrind on Freenode, but apparently > > it's not even registered. > > Er, no. We've never had an irc channel. Hmm, and with all respect, don't you think it's time to set it up? :-) BTW, thank you very much for your answers. Regards, -- Sérgio Durigan Júnior Linux on Power Toolchain - Software Engineer Linux Technology Center - LTC IBM Brazil |