# https://stackoverflow.com/questions/4254610/valgrind-reports-memory-possibly-lost-when-using-glib-data-types)
# we set some env. vars to work around them:
-function rrdtool_valgrind {
+function valgrind {
# use a sub shell, so setting environment variables only affects the current
# rrdtool run and not subsequent ones
+ local CMD="$1"
+ shift
(
G_DEBUG=gc-friendly
G_SLICE=all
--track-origins=yes \
--free-fill=ad \
$VALGRIND_OPTS \
- "$TOP_BUILDDIR/src/rrdtool" "$@"
+ "$CMD" "$@"
RC=$?
if [ -n "$VALGRIND_LOGFILE" ] ; then
case "$TESTS_STYLE" in
valgrind)
echo >&2 "# Note: exit code 111 indicates a valgrind detected memory problem"
- RRDTOOL=rrdtool_valgrind
+ RRDTOOL="valgrind $TOP_BUILDDIR/src/rrdtool"
+ RRDCACHED="valgrind $TOP_BUILDDIR/src/rrdcached"
;;
valgrind-logfile)
echo >&2 "# Note: exit code 111 indicates a valgrind detected memory problem"
- RRDTOOL=rrdtool_valgrind
+ RRDTOOL="valgrind $TOP_BUILDDIR/src/rrdtool"
+ RRDCACHED="valgrind $TOP_BUILDDIR/src/rrdcached"
VALGRIND_LOGFILE="${BASEDIR}/$(basename $0)"-valgrind.log
rm -f "$VALGRIND_LOGFILE"
;;
*)
RRDTOOL=$TOP_BUILDDIR/src/rrdtool
+ RRDCACHED=$TOP_BUILDDIR/src/rrdcached
;;
esac
fi