id	summary	reporter	owner	description	type	status	priority	milestone	version	resolution	keywords	cc	launchpad_bug
25	valgrind builder	zooko		We've had more than one issue or potential issue in pycryptopp where checking it with valgrind helps.  So far, none of the issues have turned out to be detected by valgrind, but knowing that it is valgrind-clean helps exclude a couple of classes of common bugs from consideration as explanations of the issue.  Also, of course, we might someday commit a patch to pycryptopp that has an error that is detected by valgrind.  It would be nice to have a builder that runs the pycryptopp unit tests under valgrind.  The developer can always do this manually, but having it done automatically might catch a bug if the build flags or the CPU architecture or something differ between the developer's machine and the buildslave.	enhancement	closed	minor		0.5.1	fixed	development tools, automation