|
From: Anirban J. <an...@ps...> - 2008-08-11 19:58:01
Attachments:
anirban.vcf
|
Hi, I am a new user of Valgrind. I just intalled Valgrind-3.3.1 on a Cray XT3 (AMD Opteron processors, Catamount OS on the compute nodes, SuSE Linux on the front ends). When running "make regtest" I got a few errors, that are listed below at the end of the email. Can you please advise me on whether I can afford to ignore these errors? I mainly plan to begin by using the memcheck utility, although I may use some of the other utilities later. Let me know if more information is needed. Thanks in advance Anirban ************************** Errors from regtest ------------------- == 338 tests, 25 stderr failures, 1 stdout failure, 0 post failures == memcheck/tests/malloc_free_fill (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) helgrind/tests/hg01_all_ok (stderr) helgrind/tests/hg02_deadlock (stderr) helgrind/tests/hg03_inherit (stderr) helgrind/tests/hg04_race (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc01_simple_race (stderr) helgrind/tests/tc05_simple_race (stderr) helgrind/tests/tc06_two_races (stderr) helgrind/tests/tc09_bad_unlock (stderr) helgrind/tests/tc14_laog_dinphils (stderr) helgrind/tests/tc16_byterace (stderr) helgrind/tests/tc17_sembar (stderr) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc19_shadowmem (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) helgrind/tests/tc23_bogus_condwait (stderr) |
|
From: Nicholas N. <nj...@cs...> - 2008-08-12 05:14:28
|
On Mon, 11 Aug 2008, Anirban Jana wrote: > I am a new user of Valgrind. I just intalled Valgrind-3.3.1 on a Cray XT3 > (AMD Opteron processors, Catamount OS on the compute nodes, SuSE Linux on the > front ends). When running "make regtest" I got a few errors, that are listed > below at the end of the email. Can you please advise me on whether I can > afford to ignore these errors? I mainly plan to begin by using the memcheck > utility, although I may use some of the other utilities later. Let me know if > more information is needed. Ignoring them should be fine, some of the tests aren't totally reliable, and at least some of the same tests fail on my machine. If you're really interested, you can look at the *.diff files for those tests to see how wrong they are. In a lot of cases it'll hopefully just be minor differences. Nick |