|
From: Victor R. <vm....@gm...> - 2015-10-09 16:11:51
|
On Wed, Oct 7, 2015 at 6:29 AM, Mark Wielaard <mj...@re...> wrote: > On Tue, 2015-10-06 at 19:17 -0500, Victor Rodriguez wrote: >> On Tue, Oct 6, 2015 at 5:53 PM, Rhys Kidd <rhy...@gm...> wrote: >> > What platform (OS, architecture) and Valgrind release version are you >> > running 'make regtest' on there? >> >> I am running it on Clear Linux OS ( https://clearlinux.org/) in a >> Haswell machine ( 4th generation x86) >> >> Any clue ? >> >> What does this test do ? > > The test (or actually the whole group) tests the interaction between > valgrind and gdb. It it probably a good idea to first see whether the > "basic" tools tests look sane with: make nonexp-regtest > > If those look sane then it will help to run tests that seem to hang > individually with > perl tests/vg_regtest gdbserver_tests/mcblocklistsearch.vgtest > > So try running that first outside mock and see if you can see where the > script seems to stall. > > Cheers, > > Mark Thanks a lot Mark That works just fine i had to split the test a bit caus etwo of them are hanging I remove the memcheck and none because of that reason . So my spec now looks like : 48 %build 49 # -fexceptions causes memcheck link command to fail when built with GCC 5.1 50 export CFLAGS=`echo $CFLAGS | sed s,-fexceptions,,g | sed s:-Wp,-D_FORTIFY_SOURCE=2::g | sed s:-fstack-protector::g ` 51 ./autogen.sh 52 %configure --disable-static --enable-only64bit --enable-tls 53 make V=1 %{?_smp_mflags} 54 55 %check 56 make VERBOSE=1 V=1 %{?_smp_mflags} check 57 /usr/bin/perl tests/vg_regtest cachegrind ||: 58 /usr/bin/perl tests/vg_regtest callgrind ||: 59 /usr/bin/perl tests/vg_regtest massif ||: 60 /usr/bin/perl tests/vg_regtest lackey ||: 61 /usr/bin/perl tests/vg_regtest helgrind ||: 62 /usr/bin/perl tests/vg_regtest drd ||: In the mean time we will debug what is worn and why they are hanging or failing Best Regards Victor Rodriguez |