On Wed, 27 Feb 2008, Konstantin Serebryany wrote: > My $0.02 > In my variant of helgrind I have a client request saying that we > expect a race on a particular address. > If the race is detected, the tool is silent. But if the race is *not* > detected, the tool complains at the end. > > This is not a substitute for the current testing scheme; it is quite > orthogonal. > > The current scheme tests that the output matches the golden file > (modulo addresses, tids, etc). > > My scheme is not applicable to all kinds of errors that valgrind tools > may emit and does not check the exact output. > But it is immune to changes in the test code and compiler > optimizations (inlining). > And it does not require any golden file which is useful when the test > suite is under development.
Such a test is doable within the vg_regtest framework. The .stderr.exp file will be empty (well, there'll be two blank lines in it). If the tool complains, the .stderr.out file won't match. Or have I misunderstood what you are saying? Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
