On Fri, Nov 30, 2012 at 1:42 PM, Jeffrey Walton wrote:
> On Fri, Nov 30, 2012 at 12:24 PM, NuSkooler wrote:
>> I think responses like this would be much more helpful without the FUD.
> I have no fear since I don't suffer uncertainty. The macros are broken.
>
>> WaitForSingleObject() and WaitForMu
On Fri, Nov 30, 2012 at 12:24 PM, NuSkooler wrote:
> I think responses like this would be much more helpful without the FUD.
I have no fear since I don't suffer uncertainty. The macros are broken.
> WaitForSingleObject() and WaitForMultipleObjects() return WAIT_ABANDONED if
> the mutex has been c
On 11/30/2012 6:24 PM, NuSkooler wrote:
I think responses like this would be much more helpful without the FUD.
WaitForSingleObject() and WaitForMultipleObjects() return
*WAIT_ABANDONED *if the mutex has been closed. WAIT_OBJECT_0 would only
be expected if you didn't read the documentation. I su
I think responses like this would be much more helpful without the FUD.
WaitForSingleObject() and WaitForMultipleObjects() return *WAIT_ABANDONED *if
the mutex has been closed. WAIT_OBJECT_0 would only be expected if you
didn't read the documentation. I suggest you both do so before utilizing
thes
On Thu, Nov 29, 2012 at 9:57 AM, Staneva, Yana wrote:
> Help please.
>
> I have a Win32 application (service) that loads several dlls that make
> OpenSSL calls. Also there is a separate dll that takes care of the OpenSSL
> initialization (thread setup, SSL_library_init(), SSL_CTX_new() ).
>
> I’ve
Help please.
I have a Win32 application (service) that loads several dlls that make OpenSSL
calls. Also there is a separate dll that takes care of the OpenSSL
initialization (thread setup, SSL_library_init(), SSL_CTX_new() ).
I've followed the samples online on how to do the thread setup, so I h
