>> I have used normal clamav build in a multi-threading content. >> Does it make sense to build thread-safe and not thread-safe version? >> Should I use THREAD_SAFE or CL_THREAD_SAFE preprocessor option? >> THREAD_SAFE doesn't exist in source code....
I meant CL_THREAD_SAFE by THREAD_SAFE. It definitely does make sense to build thread-safe libclamav if you intend to call more than one cl_scanfile/cl_scandesc simultaneously. I believe this is the reason for your problems. Building libclamav with CL_THREAD_SAFE would do. However, if I am right, there is an uninitialized CRITICAL_SECTION issue, that you will have to deal with. Once that is done, you should ideally have a version that you want. -- View this message in context: http://www.nabble.com/Anyone-using-clamav-on-Win32-in-multi-threaded-mode--tf3563916.html#a9964018 Sent from the clamav-win32 mailing list archive at Nabble.com. _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
