Valgrind - Revision history

Jpye: ./a4 for valgrind testing

2025-05-03T04:29:35Z

./a4 for valgrind testing

← Older revision		Revision as of 04:29, 3 May 2025
Line 2:		Line 2:

	When running ASCEND through valgrind, the following approach is suggested:		When running ASCEND through valgrind, the following approach is suggested:

			<source lang=sh>
			cd ~/ascend
			scons -j7 test a4 ascend solvers
			./a4 --valgrind test/test compiler_blackbox # or whatever the test is that you want to run
			./a4 --valgrind test/test_expectpass_leaky # a collection of calls that are known to still be leaky
			</source>

			If you don't want to use the <tt>a4</tt> script, you can set the required env vars directly:

	<source lang=sh>		<source lang=sh>

Jpye at 01:02, 4 April 2017

2017-04-04T01:02:11Z

← Older revision		Revision as of 01:02, 4 April 2017
Line 28:		Line 28:

	As [[Ben Allan]] mentioned, a '''small amount of memory leakage''' from ASCEND is perfectly tolerable, providing it is fixed in magnitude, for example global variables that do not grow in time during an ASCEND process. We have a number of such 'leakages' in ASCEND resulting from dlopening of [[external relations]] and the like. Getting rid of these leakages is difficult and has not been prioritised at this stage.		As [[Ben Allan]] mentioned, a '''small amount of memory leakage''' from ASCEND is perfectly tolerable, providing it is fixed in magnitude, for example global variables that do not grow in time during an ASCEND process. We have a number of such 'leakages' in ASCEND resulting from dlopening of [[external relations]] and the like. Getting rid of these leakages is difficult and has not been prioritised at this stage.

			The technique for adding items to the suppressions list is [https://wiki.wxwidgets.org/Valgrind_Suppression_File_Howto described in the Valgrind documention].

	[[Category:Development]]		[[Category:Development]]

Jpye at 08:15, 22 June 2011

2011-06-22T08:15:09Z

← Older revision		Revision as of 08:15, 22 June 2011
Line 24:		Line 24:

	The above approach requires that you have [http://cunit.sourceforge.net/ CUnit] installed on your system (see [[CUnit\|our notes on this]]), and that you have configured the 'scons' flags correctly so that it is detected on your system.		The above approach requires that you have [http://cunit.sourceforge.net/ CUnit] installed on your system (see [[CUnit\|our notes on this]]), and that you have configured the 'scons' flags correctly so that it is detected on your system.

			Valgrind can also be used with Python-based scripts, but you will need to be prepared to add suppressions for a large number of warnings/errors that Valgrind detects from Python itself.

			As [[Ben Allan]] mentioned, a '''small amount of memory leakage''' from ASCEND is perfectly tolerable, providing it is fixed in magnitude, for example global variables that do not grow in time during an ASCEND process. We have a number of such 'leakages' in ASCEND resulting from dlopening of [[external relations]] and the like. Getting rid of these leakages is difficult and has not been prioritised at this stage.

	[[Category:Development]]		[[Category:Development]]

Jpye at 00:38, 1 March 2011

2011-03-01T00:38:21Z

← Older revision		Revision as of 00:38, 1 March 2011
Line 23:		Line 23:
	where in the above, TESTNAME is replaced by a valid test case or test suite, use <tt>test/test -l</tt> and <tt>test/test -tSUITENAME</tt> to list available options.		where in the above, TESTNAME is replaced by a valid test case or test suite, use <tt>test/test -l</tt> and <tt>test/test -tSUITENAME</tt> to list available options.

	The above approach requires that you have [http://cunit.sourceforge.net/ CUnit] installed on your system, and that you have configured the 'scons' flags correctly so that it is detected on your system.		The above approach requires that you have [http://cunit.sourceforge.net/ CUnit] installed on your system (see [[CUnit\|our notes on this]]), and that you have configured the 'scons' flags correctly so that it is detected on your system.

	[[Category:Development]]		[[Category:Development]]

Jpye at 06:43, 15 February 2011

2011-02-15T06:43:07Z

← Older revision		Revision as of 06:43, 15 February 2011
Line 4:		Line 4:

	<source lang=sh>		<source lang=sh>
			# enter your working directory
			cd ~/ascend

			# build the test suite, plus libascend (dependency)
	scons -j2 test		scons -j2 test

			# you might also need to build the solvers as another step
			scons -j2 solvers

			# set up your runtime environment
	export ASCENDLIBRARY=~/ascend/models		export ASCENDLIBRARY=~/ascend/models
	export LD_LIBRARY_PATH=~/ascend:/usr/lib/coin:/usr/lib/coin/ThirdParty		export LD_LIBRARY_PATH=~/ascend:/usr/lib/coin:/usr/lib/coin/ThirdParty

			# run the test suite through valgrind in 'memcheck' mode:
	valgrind --suppressions=tools/valgrind/suppressions --tool=memcheck --leak-check=full --show-reachable=yes test/test TESTNAME		valgrind --suppressions=tools/valgrind/suppressions --tool=memcheck --leak-check=full --show-reachable=yes test/test TESTNAME
	</source>		</source>

Jpye: Created page with '[http://valgrind.org/ Valgrind] is a tool that can detect memory leaks and invalid attempts to access memory, or perform actions that depend on the contents of uninitialised memo…'

2011-01-06T00:36:46Z

Created page with '[http://valgrind.org/ Valgrind] is a tool that can detect memory leaks and invalid attempts to access memory, or perform actions that depend on the contents of uninitialised memo…'

New page

[http://valgrind.org/ Valgrind] is a tool that can detect memory leaks and invalid attempts to access memory, or perform actions that depend on the contents of uninitialised memory.

When running ASCEND through valgrind, the following approach is suggested:

<source lang=sh>
scons -j2 test
export ASCENDLIBRARY=~/ascend/models
export LD_LIBRARY_PATH=~/ascend:/usr/lib/coin:/usr/lib/coin/ThirdParty
valgrind --suppressions=tools/valgrind/suppressions --tool=memcheck --leak-check=full --show-reachable=yes test/test TESTNAME
</source>

where in the above, TESTNAME is replaced by a valid test case or test suite, use <tt>test/test -l</tt> and <tt>test/test -tSUITENAME</tt> to list available options.

The above approach requires that you have [http://cunit.sourceforge.net/ CUnit] installed on your system, and that you have configured the 'scons' flags correctly so that it is detected on your system.

[[Category:Development]]