> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Dan Heinz
> Sent: Thursday, August 15, 2019 13:19
> blows up. Not entirely conventional, but it might be revealing.
>
> It is actually in a call to libxml2 and does not
> appear to be related to OpenSSL. Now I just
>The output certainly suggests something is calling TlsAlloc between the call
>made for destructor_key.value and the one for private_drbg, and that index is
>never freed. You always get 7 when allocating destructor_key.value because
>that >index was freed when you unloaded OpenSSL, and so it's
The output certainly suggests something is calling TlsAlloc between the call
made for destructor_key.value and the one for private_drbg, and that index is
never freed. You always get 7 when allocating destructor_key.value because that
index was freed when you unloaded OpenSSL, and so it's the
On 13/08/2019 19:16, Dan Heinz wrote:
> On 09/08/2019 14:33, Dan Heinz wrote:
>>> I have a static library using OpenSSL (built as static library with the
>>> no-pinshared parameter in the configuration) that is then included in a
>>> DLL that gets loaded and unloaded many times by the calling
On 09/08/2019 14:33, Dan Heinz wrote:
>> I have a static library using OpenSSL (built as static library with
>> the no-pinshared parameter in the configuration) that is then included
>> in a DLL that gets loaded and unloaded many times by the calling
>> application. Now that the code is in
On 09/08/2019 14:33, Dan Heinz wrote:
> I have a static library using OpenSSL (built as static library with the
> no-pinshared parameter in the configuration) that is then included in a DLL
> that
> gets loaded and unloaded many times by the calling application. Now that the
> code is in
