summaryrefslogtreecommitdiffstats
path: root/src/kdc/Makefile.in
diff options
context:
space:
mode:
authorKen Raeburn <raeburn@mit.edu>2006-10-13 23:54:24 +0000
committerKen Raeburn <raeburn@mit.edu>2006-10-13 23:54:24 +0000
commit2720291460e1e211be215fddb8096e3ed1d9bb28 (patch)
treeb4756498450fc19aba40eb171dbffb91791a9582 /src/kdc/Makefile.in
parentc59d1c439d08bde8e10f6a9e73ad753f7968503c (diff)
downloadkrb5-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/kdc/Makefile.in')
-rw-r--r--src/kdc/Makefile.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/kdc/Makefile.in b/src/kdc/Makefile.in
index 33bb2728f1..0c3a161a56 100644
--- a/src/kdc/Makefile.in
+++ b/src/kdc/Makefile.in
@@ -72,7 +72,7 @@ fakeka: fakeka.o $(KADMSRV_DEPLIBS) $(KRB4COMPAT_DEPLIBS) $(APPUTILS_DEPLIB)
check-unix:: rtest
KRB5_CONFIG=$(SRCTOP)/config-files/krb5.conf ; export KRB5_CONFIG ;\
- $(RUN_SETUP) $(srcdir)/rtscript > test.out
+ $(RUN_SETUP) $(VALGRIND) $(srcdir)/rtscript > test.out
cmp test.out $(srcdir)/rtest.good
$(RM) test.out