livetrax/gtk2_ardour/armass

#!/bin/sh
MASSIF_OPTIONS="$MASSIF_OPTIONS --time-unit=ms"

TOP=`dirname "$0"`/..
. $TOP/build/gtk2_ardour/ardev_common_waf.sh
export ARDOUR_RUNNING_UNDER_VALGRIND=TRUE
exec valgrind --tool=massif \
	$MASSIF_OPTIONS \
	$TOP/$EXECUTABLE --novst "$@"

# analyse output with
#   ms_print massif.out.<PID>
# or check out https://projects.kde.org/projects/extragear/sdk/massif-visualizer
add script to run ardour in valgrind/massif 2014-10-10 09:03:26 -04:00			`#!/bin/sh`
fun with valgrind 2015-10-27 06:15:34 -04:00			`MASSIF_OPTIONS="$MASSIF_OPTIONS --time-unit=ms"`
Use ardev_common.sh to setup environment for running libardour tests 2014-11-29 08:42:21 -05:00
			TOP=`dirname "$0"`/..
			`. $TOP/build/gtk2_ardour/ardev_common_waf.sh`
add script to run ardour in valgrind/massif 2014-10-10 09:03:26 -04:00			`export ARDOUR_RUNNING_UNDER_VALGRIND=TRUE`
fun with valgrind 2015-10-27 06:15:34 -04:00			`exec valgrind --tool=massif \`
			`$MASSIF_OPTIONS \`
add script to run ardour in valgrind/massif 2014-10-10 09:03:26 -04:00			`$TOP/$EXECUTABLE --novst "$@"`
amend previous commit blame gitx 0.15.1949: it updates the stage view even though the changes are not staged. 2014-10-10 09:24:52 -04:00
			`# analyse output with`
			`# ms_print massif.out.<PID>`
			`# or check out https://projects.kde.org/projects/extragear/sdk/massif-visualizer`