p11-kit.git - Clone of https://github.com/p11-glue/p11-kit

	Commit message (Collapse)	Author	Age	Files	Lines
*	Our own unit testing framework	Stef Walter	2013-05-21	1	-4/+1
\| \| \| \| \| \| \| \|	* Support the TAP protocol * Much cleaner without having to carry around state * First class support for setup/teardown * Port the common tests * Wait on porting other tests until we've merged outstanding code
*	Implement valgrind's hellgrind checks for threading problems	Stef Walter	2013-05-15	1	-0/+5
\| \| \| \| \| \| \|	And cleanup our locks/locking model. There's no need to use recursive locks, especially since we can't use them on all platforms. In addition adjust taking of locks during initialization so that there's no chance of deadlocking here.
*	Add a bit of infrastructure for running valgrind	Stef Walter	2013-03-20	1	-0/+11
\| \| \| \| \|	* make memcheck: Runs basic memory checking * make leakcheck: Also runs leak checking
*	Move debug and library code into the common/ subdirectory	Stef Walter	2013-01-09	1	-0/+8
	Start using p11_ as our internal prefix rather than _p11_. We explicitly export p11_kit_ so this is fine as far as visibility. Move the threading, mutex, and module compat, dict, and array code into the common directory too. Take this opportunity to clean up a bit of internal API as well, since so many lines are being touched internally.