tree 2ae4363df638ba3a9db5151ae6198d881a2f9618
parent cca972553c13aff57cf4c13551b1dda1a522132e
author nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> 1097743086 +0000
committer nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> 1097743086 +0000

Added a unit self-test -- a test program that incorporates a small part of
Valgrind itself (the files ume.c, ume_entry.c and jmp_with_stack.c).  Thus,
we are using Memcheck to check these files in a unit test setting.

I hope to do unit self-testing for many more parts of Valgrind, eventually all
the bits that can be pulled out into any kind of sensible stand-alone form.
Doing so achieves two things:

 a) it introduces unit testing into our framework (a serious shortcoming at the
    moment)
 b) it lets us use Valgrind (esp. Memcheck) on itself, to some extent

This should help reliability.  This first unit self-test isn't very exhaustive,
but it's a start.

Note that this involves something like bootstrapping, in that we are checking
parts of a Valgrind build with itself.  I don't think this will be a problem,
since we (at least, I do) tend to only run the regtests when we think the
Valgrind build is ok.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2760 a5019735-40e9-0310-863c-91ae7b9d1cf9