|
From: Christian B. <bor...@de...> - 2012-05-08 02:05:26
Attachments:
diffs.txt
|
valgrind revision: 12557 VEX revision: 2324 C compiler: gcc (SUSE Linux) 4.3.4 [gcc-4_3-branch revision 152973] Assembler: GNU assembler (GNU Binutils; SUSE Linux Enterprise 11) 2.20.0.20100122-0.7.9 C library: GNU C Library stable release version 2.11.1 (20100118) uname -mrs: Linux 2.6.32.54-0.3-default s390x Vendor version: Welcome to SUSE Linux Enterprise Server 11 SP1 (s390x) - Kernel %r (%t). Nightly build on sless390 ( SUSE Linux Enterprise Server 11 SP1 gcc 4.3.4 on z196 (s390x) ) Started at 2012-05-08 03:45:01 CEST Ended at 2012-05-08 04:05:15 CEST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 526 tests, 4 stderr failures, 0 stdout failures, 6 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcbreak (stderrB) gdbserver_tests/mcclean_after_fork (stderrB) gdbserver_tests/mcleak (stderrB) gdbserver_tests/mcmain_pic (stderrB) gdbserver_tests/mcvabits (stderrB) gdbserver_tests/mssnapshot (stderrB) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/tc04_free_lock (stderr) drd/tests/tc09_bad_unlock (stderr) |
|
From: Christian B. <bor...@de...> - 2012-05-08 19:35:48
|
> gdbserver_tests/mcbreak (stderrB) > gdbserver_tests/mcclean_after_fork (stderrB) > gdbserver_tests/mcleak (stderrB) > gdbserver_tests/mcmain_pic (stderrB) > gdbserver_tests/mcvabits (stderrB) > gdbserver_tests/mssnapshot (stderrB) [...] Philippe, those errors started on may 3rd. I checked the system and the admin has installed a new version of libc (and some other updates). Can you have a look if the diff makes sense to you and know a trivial fix? Christian |
|
From: Philippe W. <phi...@sk...> - 2012-05-08 20:23:33
|
On Tue, 2012-05-08 at 21:35 +0200, Christian Borntraeger wrote: Hello Christian, > > gdbserver_tests/mcbreak (stderrB) > > gdbserver_tests/mcclean_after_fork (stderrB) > > gdbserver_tests/mcleak (stderrB) > > gdbserver_tests/mcmain_pic (stderrB) > > gdbserver_tests/mcvabits (stderrB) For this, there are new empty lines in the output which makes the diff failing. I have a guess below about why we have these empty lines. > > gdbserver_tests/mssnapshot (stderrB) For this, gdb outputs a message that some debug info is missing. This msg is making the diff failing. This can be fixed by installing the missing debug info : + + +Missing separate debuginfo for /lib64/libpthread.so.0 +Try: zypper install -C "debuginfo(build-id)=13e490fdfaa1228f704434346135690d1ae5e250" + + +Missing separate debuginfo for /lib64/libc.so.6 +Try: zypper install -C "debuginfo(build-id)=85816bf964a7b4595860d8e75ed7ebb2d15c8d1b" The "missing debug info" is (supposed to be) filtered by filter_memcheck_monitor. However, I believe that the filter might not be good enough, and keeps empty lines surrounding the 'Missing' and 'Try' lines. The mssnapshot test does not have such filtering, and so we see the full excess lines. => so, it might be that installing the missing debug info will solve all the problems. If not all problems are solved, can you do: perl tests/vg_regtest --keep-unfiltered gdbserver_tests and send me a tgz of the .out files created in the gdbserver_tests dir ? Thanks Philippe Note: the filtering logic in the gdbserver tests is a nasty problem as it is impacted by the glibc behaviour, the kernel and the version of gdb. And moreover, this filtering is really not a piece of code I can be proud of. |