| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Test runner checks for leaks when leak detective is enabled.
|
|
|
|
|
|
| |
Passing integers of unspecified length may result in passing an integer shorter
than uintptr_t. When reading them back, we might get more data than passed,
resulting in a failure.
|
| |
|
| |
|
|
|
|
| |
But of course backtracing must be initialized anyway using backtrace_init().
|
|
|
|
|
|
| |
As we don't depend on the check framework anymore, we can enable the unit tests
by default. These are built/executed with "make check" only, so it makes no
sense to disable them.
|
| |
|
|
|
|
|
| |
On OS X Mavericks, these functions use a static allocation and are hard
to whitelist using other means.
|
|
|
|
|
| |
If we initialize libstrongswan more than once in the same process, we may
not register the hooks twice.
|
|
|
|
| |
This resets leak detective state should it get created/destroyed more than once.
|
|
|
|
| |
This is more flexible than printing reports to a FILE.
|
| |
|
|
|
|
| |
Fixes #437.
|