|
From: Philippe W. <phi...@sk...> - 2011-11-17 22:36:27
|
I have finished setting up the nightly regression test on ppc64/fedora16. Find below the results + a quick analysis of the failures. Reasons 1 to 4 are real bugs or probable bugs in Valgrind on ppc64/fedora16. 5 to 9 are probably not bugs, but rather tests behaving slightly differently. If nobody complains about the below telling it is unusable, I will enable the sending of the results on the valdev mailing list. Thanks Philippe == 504 tests, 10 stderr failures, 8 stdout failures, 1 stderrB failure, 1 stdoutB failure, 2 post failures == gdbserver_tests/mcmain_pic (stdout) gdbserver_tests/mcmain_pic (stderr) gdbserver_tests/mcmain_pic (stdoutB) gdbserver_tests/mcmain_pic (stderrB) memcheck/tests/ppc32/power_ISA2_05 (stdout) memcheck/tests/ppc32/power_ISA2_05 (stderr) memcheck/tests/ppc64/power_ISA2_05 (stdout) memcheck/tests/ppc64/power_ISA2_05 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/wrap8 (stdout) memcheck/tests/wrap8 (stderr) massif/tests/big-alloc (post) massif/tests/deep-D (post) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-vmx (stdout) none/tests/ppc64/jm-fp (stdout) none/tests/ppc64/jm-vmx (stdout) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/tc04_free_lock (stderr) drd/tests/tc09_bad_unlock (stderr) 1. line nr difference in a stack trace: it looks like the end of the function is located on the closing bracket on other platforms, on the last line containing real code on this platform. ./valgrind-new/drd/tests/tc04_free_lock.stderr.diff ./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff ./valgrind-new/memcheck/tests/varinfo6.stderr.diff-ppc64 2. different numerical results ? ./valgrind-new/none/tests/ppc32/jm-fp.stdout.diff ./valgrind-new/none/tests/ppc32/jm-vmx.stdout.diff ./valgrind-new/none/tests/ppc32/jm-vmx.stdout.diff_Minus_nan ./valgrind-new/none/tests/ppc64/jm-fp.stdout.diff ./valgrind-new/none/tests/ppc64/jm-vmx.stdout.diff ./valgrind-new/none/tests/ppc64/jm-vmx.stdout.diff_Minus_nan 3. internal error in ld.so when running under valgrind a PIC executable: ./valgrind-new/gdbserver_tests/mcmain_pic.stderr.diff 4. SIGSEGV ./valgrind-new/memcheck/tests/ppc32/power_ISA2_05.stderr.diff ./valgrind-new/memcheck/tests/ppc32/power_ISA2_05.stdout.diff ./valgrind-new/memcheck/tests/ppc64/power_ISA2_05.stderr.diff ./valgrind-new/memcheck/tests/ppc64/power_ISA2_05.stdout.diff 5. semaphore operations failed with ENOSYS instead of expected EINVAL. ./valgrind-new/helgrind/tests/tc18_semabuse.stderr.diff ./valgrind-new/helgrind/tests/tc20_verifywrap.stderr.diff 6. Small differences in the nr bytes allocated. ./valgrind-new/massif/tests/big-alloc.post.diff 7. Stack trace difference for a "below main" stack trace. ./valgrind-new/massif/tests/deep-D.post.diff 8. badjump.c produces an invalid jump rather than just an access not within mapped region. ./valgrind-new/memcheck/tests/supp_unknown.stderr.diff 9. Stack overflow on ppc64 (which is a normal "crash") produces a different stack trace (but still detects the crash). ./valgrind-new/memcheck/tests/wrap8.stderr.diff |