|
From: Maynard J. <may...@us...> - 2011-10-10 13:16:08
|
Philippe Waroquiers wrote: >> The regression tests on POWER7/SLES 11 SP1 (using Oct 6, 2011 SVN) actually compare quite favorably to Valgrind 3.6.1 on a POWER5 >> (POWER7 support did not yet exist in 3.6.1 timeframe). For reference, here are the results: > > The attached diff files also contains differences for mcbreak, but mcbreak is not in the below list ??? Right . . . copy/paste error. >> gdbserver_tests/mcinfcallRU (stderr) >> gdbserver_tests/mcinfcallWSRU (stderr) >> gdbserver_tests/mcinfcallWSRU (stderrB) > These 3 failures+the mcbreak seems linked to problems to do an inferior function call. > (see below). > >> gdbserver_tests/mcsignopass (stderr) >> gdbserver_tests/mcsignopass (stdoutB) >> gdbserver_tests/mcsigpass (stderr) >> gdbserver_tests/mcsigpass (stdoutB) > The above tests are based on none/tests/faultstatus which also fails. > I think that if faultstatus is fixed, these should also work. OK, I'll look at faultstatus. > >> gdbserver_tests/nlcontrolc (stdoutB) >> gdbserver_tests/nlpasssigalrm (stdoutB) > These two are failing as the filter script does not properly remove or transform > the power7 specific line: > from /lib64/power7/libc.so.6 > and > 0x........ in .__GI_kill () from /lib64/power7/libc.so.6 > The (already horrible) gdbserver_tests/filter_gdb should be further enhanced to filter or transform these. Should I open a bug report and attach a patch for this? > ... >> Unfortunately, POWER5/SLES 10 SP3 (current SVN) compared much worse to Valgrind 3.6.1 -- lots of callgrind and helgrind failures. >> Whereas results from an April 15 snapshot of SVN was almost identical to the 3.6.1 results (with just two extra callgrind >> testcases failing). >> Also, some gdbserver tests usually hang the regtest on this processor; thus, I have to remove the gdbserver/*vgtest files in order >> to get >> 'make regtest' to complete. I have seen occasional hangs of gdbserver tests on POWER7, too, but not often. > > Hanging tests are often caused by inferior function calls not working properly. A possible technique to investigate this > is to compare the behaviour of the "standard" gdbserver with the valgrind gdbserver > (see gdbserver_tests/README_DEVELOPERS). I'll try to find some time to look at this later in the week. Thanks for the help! -Maynard > > Philippe > |