From 2720291460e1e211be215fddb8096e3ed1d9bb28 Mon Sep 17 00:00:00 2001 From: Ken Raeburn Date: Fri, 13 Oct 2006 23:54:24 +0000 Subject: 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 --- src/kdc/Makefile.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/kdc/Makefile.in') diff --git a/src/kdc/Makefile.in b/src/kdc/Makefile.in index 33bb272..0c3a161 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 -- cgit v1.1