On Wed, 2014-09-03 at 21:02 +0200, Florian Krohm wrote: > I reran the regtest and this time the test passed. That does not sound > good. Looks like I should run memcheck on helgrind.... I did run the full test suite in an outer memcheck some days ago. Did not find anything wrong; but the difficulty with some tests (in particular with memcheck tests) is that the wrong behaviour in the test is causing the outer memchecvk to detect a bug in the JITted code generated for the misbheaving test case.
But for hg05_race2, no error reported by memcheck. Note however that helgrind test cases are not (necessarily) deterministic. Sometimes, depending on thread scheduling, you have (or not errors). So, we can imagine that the race is sometimes detected in one thread; sometimes in the other, and then we have 'lost' the exact place at which the race happened. Would be worth trying with --fair-sched=yes and see if that is more reproducable Philippe > > 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 ------------------------------------------------------------------------------ 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
