diff options
| author | Ken Raeburn <raeburn@mit.edu> | 2006-10-13 23:54:24 +0000 |
|---|---|---|
| committer | Ken Raeburn <raeburn@mit.edu> | 2006-10-13 23:54:24 +0000 |
| commit | 2720291460e1e211be215fddb8096e3ed1d9bb28 (patch) | |
| tree | b4756498450fc19aba40eb171dbffb91791a9582 /src/util/et | |
| parent | c59d1c439d08bde8e10f6a9e73ad753f7968503c (diff) | |
| download | krb5-2720291460e1e211be215fddb8096e3ed1d9bb28.tar.gz krb5-2720291460e1e211be215fddb8096e3ed1d9bb28.tar.xz krb5-2720291460e1e211be215fddb8096e3ed1d9bb28.zip | |
Use $(VALGRIND) when running programs using $(KRB5_RUN_ENV) or
$(RUN_SETUP). Replaces old hack with MAYBE_VALGRIND added to RUN_ENV
in a way that would break in some of the tests.
Set VALGRIND in site.exp in tests/dejagnu. (Not used yet.)
Runs some shell scripts under valgrind, rather than changing them to
run only the executables under valgrind; this is mostly okay, just
creates lots of extra log data, and requires --trace-children=yes.
This should work for any instrumentation program invocation that gets
followed immediately by the name and argument list for the program
being instrumented. For example, VALGRIND="env LD_PRELOAD=..." should
work, though I haven't tested it.
git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@18699 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/util/et')
| -rw-r--r-- | src/util/et/Makefile.in | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/util/et/Makefile.in b/src/util/et/Makefile.in index fd3112963..b7aa747a8 100644 --- a/src/util/et/Makefile.in +++ b/src/util/et/Makefile.in @@ -161,8 +161,8 @@ RUN_SETUP = @KRB5_RUN_ENV@ # test_et doesn't have an interesting exit status, but it'll exercise # some cases that t_com_err doesn't, so let's see if it crashes. check-unix:: t_com_err test_et - $(RUN_SETUP) ./test_et - $(RUN_SETUP) ./t_com_err + $(RUN_SETUP) $(VALGRIND) ./test_et + $(RUN_SETUP) $(VALGRIND) ./t_com_err check-windows:: $(OUTPRE)test_et$(EXEEXT) set path=$(BUILDTOP)\lib\$(OUTPRE);%path%; |