summaryrefslogtreecommitdiff
path: root/tests/test-init.c
Commit message (Collapse)AuthorAgeFilesLines
* Move debug and library code into the common/ subdirectoryStef Walter2013-01-091-319/+0
| | | | | | | | | | | 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.
* Use correct shared library extension on windowsStef Walter2012-07-261-1/+1
| | | | | | | | * The windows shared libraries have the .dll extension * This means we also need separate directories for the test module configs on win32 https://bugzilla.gnome.org/show_bug.cgi?id=44740
* Preconditions to check for input probs and out of memoryStef Walter2012-05-131-1/+67
| | | | | | * We don't try to guarantee completely robust and problem free behavior in cases where the caller or process isn't behaving. We consider these to be outside of our control.
* Move the compat.[ch] headers into common directory/Stef Walter2012-04-301-1/+1
| | | | | * And the compat stuff in the p11-kit directory merged into util.c and util.h
* Compile CuTest.c separately.Andreas Metzler2011-12-231-2/+0
| | | | | Use regular compile and link instead of having #include "CuTest.c" in every test. Works around gcc optimization issue.
* Rename non-static functions to have a _p11_xxx prefix.Stef Walter2011-10-241-11/+11
| | | | | | | * Work around issues with brain-dead linkers not respecting the libtool -export-symbol-regex argument https://bugs.freedesktop.org/show_bug.cgi?id=42020
* Initial port to win32Stef Walter2011-10-171-24/+32
| | | | | | | | * Tests do not all yet pass, at least not on wine * Added abstraction of some non-portable functions in compat.h/c * Build with an argument like this for win32 support: ./autogen.sh --host=i586-mingw32msvc * This win32 port needs more work from interested parties
* Only call C_Initialize and C_Finalize once per moduleStef Walter2011-10-101-1/+104
| | | | | | | | * Do not concurretnly call C_Initialize or C_Finalize in a module * The PKCS#11 spec indicates that mone thread should call those functions. * It's reasonable for a module to expect to only be initialized or finalized in one thread. * In particular NSS does not lock its C_Initialize or C_Finalize.
* Combine initialization testsStef Walter2011-10-101-0/+144