Quick hack to make it easy to run valgrind on many of our test cases.
authorKen Raeburn <raeburn@mit.edu>
Thu, 16 Mar 2006 01:29:26 +0000 (01:29 +0000)
committerKen Raeburn <raeburn@mit.edu>
Thu, 16 Mar 2006 01:29:26 +0000 (01:29 +0000)
Notably, though, the dejagnu tests will not include valgrind.

* pre.in (MAYBE_VALGRIND): New variable.
* shlib.conf (*-*-linux*): Use it in RUN_ENV.

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@17742 dc483132-0cff-0310-8789-dd5450dbe970

src/config/ChangeLog
src/config/pre.in
src/config/shlib.conf

index 481de61adee510137c0e89f24ed846cbf7c6d549..b14a4ce067025b29eecf6534a646a65bd7f1422b 100644 (file)
@@ -1,3 +1,8 @@
+2006-03-15  Ken Raeburn  <raeburn@mit.edu>
+
+       * pre.in (MAYBE_VALGRIND): New variable.
+       * shlib.conf (*-*-linux*): Use it in RUN_ENV.
+
 2006-03-11  Ken Raeburn  <raeburn@mit.edu>
 
        * pre.in (KRB_INCLUDES): Drop include/krb5 directories.
index 02aa7546139698f4e6e5a2ce8f84206855f9a17f..de7f6d4552ef0f9c23cad7b4f5a325c8beac9a40 100644 (file)
@@ -546,7 +546,9 @@ PROFFLAGS=@PROFFLAGS@
 # platform-dependent temporary files that should get cleaned up
 EXTRA_FILES=@EXTRA_FILES@
 
-
+# The "env" at the end is because sometimes we add local environment
+# variable settings with "@RUN_ENV@ KRB5_CONFIG=foo ..."
+MAYBE_VALGRIND= # valgrind --tool=memcheck --log-file=$(BUILDTOP)/valgrind.out --trace-children=yes -v --leak-check=yes env
 
 ##
 ## end of pre.in
index 744d7ea053db3d8c817bb3be988c18f3b4a729df..cc914577d017a895f5566d0e596658eb0047ac9e 100644 (file)
@@ -360,7 +360,7 @@ mips-*-netbsd*)
        RPATH_FLAG='-Wl,-rpath -Wl,'
        CC_LINK_SHARED='$(CC) $(PROG_LIBPATH) $(RPATH_FLAG)$(PROG_RPATH) $(CFLAGS) $(LDFLAGS)'
        CC_LINK_STATIC='$(CC) $(PROG_LIBPATH) $(CFLAGS) $(LDFLAGS)'
-       RUN_ENV='LD_LIBRARY_PATH=`echo $(PROG_LIBPATH) | sed -e "s/-L//g" -e "s/ /:/g"`; export LD_LIBRARY_PATH;'
+       RUN_ENV='LD_LIBRARY_PATH=`echo $(PROG_LIBPATH) | sed -e "s/-L//g" -e "s/ /:/g"`; export LD_LIBRARY_PATH; $(MAYBE_VALGRIND)'
 
        ## old version:
        # Linux libc does weird stuff at shlib link time, must be