testsuite: expand DYNINST_REWRITER_NO_UNLINK such that unique filenames are produced...
authorJames Waskiewicz <jaw@armour.cs.umd.edu>
Fri, 19 Jun 2009 18:24:28 +0000 (14:24 -0400)
committerJames Waskiewicz <jaw@armour.cs.umd.edu>
Fri, 19 Jun 2009 18:24:28 +0000 (14:24 -0400)
commitf712bc5ca3815c7c773142f298c55555fa166283
tree804cbd24d68b9687ccb1307df5446a1fd38b6e8d
parent88746d5f10aa67a65676017de6e08295700a7fe8
testsuite:  expand DYNINST_REWRITER_NO_UNLINK such that unique filenames are produced for each rungroup, this ensures that binaries are not overwritten by each successive group.  For a given rungroup, only a subset of the rewriter tests will be valid.  This also creates a report file, one per rewritten binary, that contains the list of
tests that were implemented in that particular binary.

Also, if, in a rungroup, one test fails or crashes, all tests in the group were marked with failure.  This changes that:  now if a rewritten mutatee crashes or reports failure, the rungroup is broken apart into individual tests, with each being run seperately to provide a finer grain of reporting on what succeeded and what failed.
parseThat/src/dyninstCore.C
testsuite/src/dyninst/ParseThat.C
testsuite/src/dyninst/test1_1_mutatee.c
testsuite/src/dyninst/test_lib_mutateeStart.C
testsuite/src/mutatee_driver.c