Jakub Adam 73888a57c2 Ensure threads have finished using a barrier before releasing it ... MSDN documentation says it is ensured that all threads in the barrier have finished using it before allowing the barrier to be released in DeleteSynchronizationBarrier(). The winpr re-implementation wasn't keeping to that requirement, which was causing occasional crashes when shadow client tried to access already freed barrier structure. The crash was occuring in winpr_Handle_cleanup() after finished waiting on a barrier's event.		2015-05-22 13:36:15 +02:00
..
include	Merge pull request #2596 from akallabeth/wlog_default_out_fix	2015-05-08 00:49:41 +02:00
libwinpr	Ensure threads have finished using a barrier before releasing it	2015-05-22 13:36:15 +02:00
tools	free can handle NULL perfectly fine	2015-05-11 09:07:39 +02:00
.gitignore	libwinpr-registry: start implementation	2012-06-05 18:56:31 -04:00
CMakeLists.txt	winpr: always build "monolitic"	2014-07-10 11:10:58 +02:00
WinPRConfig.cmake.in	cmake: export to different directory, export more build info	2013-10-29 15:16:44 -04:00