projects / strongswan.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 6250e81) | patch
leak-detective: Whitelist thread ID getter
authorTobias Brunner <tobias@strongswan.org>
Tue, 13 Sep 2016 15:28:21 +0000 (17:28 +0200)
committerTobias Brunner <tobias@strongswan.org>
Tue, 20 Sep 2016 14:26:05 +0000 (16:26 +0200)
commit95f9fa82d5574f08dca873941115ce60c8f14341
tree9563d3259b054385a7fb7fa32c853e1290bde404tree | snapshot
parent6250e813ca8f4a70e3f96f13c08415548de62e52commit | diff
leak-detective: Whitelist thread ID getter

In case an external thread calls into our code and logs messages, a thread
object is allocated that will never be released.  Even if we try to clean
up the object via thread value destructor there is no guarantee that the
thread actually terminates before we check for leaks, which seems to be the
case for the Ada Tasking threads.
src/libstrongswan/utils/leak_detective.c diff | blob | history
strongSwan - IPsec VPN