On 03.09.2014 19:02, Florian Krohm wrote: > On 03.09.2014 13:03, Julian Seward wrote: >> >> A beta tarball for 3.10.0 is available now at >> http://www.valgrind.org/downloads/valgrind-3.10.0.BETA1.tar.bz2 >> (md5sum = dee188c79a9795fee178ba17f42c40b3) > > I just tested this on my x86-64. I see one unexpected failure in the > testsuite: > > helgrind/tests/hg05_race2 > fails like so: > > --- hg05_race2.stderr.exp 2014-09-02 12:32:36.000000000 +0200 > +++ hg05_race2.stderr.out 2014-09-03 17:47:06.739851222 +0200 > @@ -26,8 +26,7 @@ > at 0x........: th (hg05_race2.c:17) > by 0x........: mythread_wrapper (hg_intercepts.c:...) > ... > - Location 0x........ is 0 bytes inside foo.poot[5].plop[11], > - declared at hg05_race2.c:24, in frame #x of thread x > + Address 0x........ is on thread #x's stack > > ---------------------------------------------------------------- > > @@ -42,8 +41,7 @@ > at 0x........: th (hg05_race2.c:17) > by 0x........: mythread_wrapper (hg_intercepts.c:...) > ... > - Location 0x........ is 0 bytes inside foo.poot[5].plop[11], > - declared at hg05_race2.c:24, in frame #x of thread x > + Address 0x........ is on thread #x's stack > > > THis is with gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2. Is this a known issue?
I reran the regtest and this time the test passed. That does not sound good. Looks like I should run memcheck on helgrind.... Florian ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
