Following up on this somewhat old thread just to correct some
misunderstandings about the nature of the Windows APIs.
On 25/01/2015 19:49, Michel SALES wrote:
Hi Avery,
In the code I sent over before, I was calling CloseHandle on the thread:
HANDLE h1=CreateThread(0,0,thread1,0,0,t1);
Following up on this somewhat old thread just to correct some
misunderstandings about the nature of the Windows APIs.
On 25/01/2015 19:49, Michel SALES wrote:
Hi Avery,
In the code I sent over before, I was calling CloseHandle on the thread:
HANDLE h1=CreateThread(0,0,thread1,0,0,t1);
: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL
1.0.1l
Hi Michel,
It doesn't appear to be related to that. I added CloseHandle's and got the
same result.
Here are my updated findings... The following simple program still causes
the same Handle Leaks...
Important findings:
1
it helps,
Michel
De : openssl-users [mailto:openssl-users-boun...@openssl.org] De la part de
Avery A. Tarasov
Envoyé : samedi 24 janvier 2015 22:34
À : openssl-users@openssl.org
Objet : Re: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL
1.0.1l
Hi Michel,
It doesn't appear to be related
Hi Avery,
In the code I sent over before, I was calling CloseHandle on the thread:
HANDLE h1=CreateThread(0,0,thread1,0,0,t1); if(h1==0) { return
0; } CloseHandle(h1);
Yes, but you were trying to close the handle of a thread which was still
running !
I have not checked what happens in this
On Sat, Jan 24, 2015 at 04:34:14PM -0500, Avery A. Tarasov wrote:
Important findings:
*1) * IfSSL_library_init() and SSL_load_error_strings() are *removed*
(which are the only 2 OpenSSL functions I'm using) the handle leaks go
away..
*2)* IfSSL_library_init() and
: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL
1.0.1l
Hi Michel,
It doesn't appear to be related to that. I added CloseHandle's and got the
same result.
Here are my updated findings... The following simple program still causes
the same Handle Leaks...
Important findings:
1
it helps,
Michel
De : openssl-users [mailto:openssl-users-boun...@openssl.org] De la part de
Avery A. Tarasov
Envoyé : samedi 24 janvier 2015 22:34
À : openssl-users@openssl.org
Objet : Re: [openssl-users] Handle Leaks - shmem-win32.c shmem.c - OpenSSL
1.0.1l
Hi Michel,
It doesn't appear to be related
Hi Avery,
In the code I sent over before, I was calling CloseHandle on the thread:
HANDLE h1=CreateThread(0,0,thread1,0,0,t1); if(h1==0) { return
0; } CloseHandle(h1);
Yes, but you were trying to close the handle of a thread which was still
running !
I have not checked what happens in this
Hi Michel,
I actually already tried _beginthread but got the same results.
CrtDumpMemoryLeaks also reports no problems for me. I guess the tool I
was using for leak detection just has some bugs in it.
Thanks again for your help.
Best Regards,
-Avery
On 1/25/2015 1:49 PM, Michel SALES
Hi Michel,
It doesn't appear to be related to that. I added CloseHandle's and got
the same result.
Here are my updated findings... The following simple program still
causes the same Handle Leaks...
Important findings:
*1) * IfSSL_library_init() and SSL_load_error_strings() are
Hi,
Just a quick answer : I didn't find any call to CloseHandle() function in your
code.
Best regards,
Michel.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi Michel,
It doesn't appear to be related to that. I added CloseHandle's and got
the same result.
Here are my updated findings... The following simple program still
causes the same Handle Leaks...
Important findings:
*1) * IfSSL_library_init() and SSL_load_error_strings() are
I have a fairly simple Win32 application (.cpp file source code
attached) that uses OpenSSL 1.0.1l to send some GET requests in 2
threads. I am getting reports of Handle Leaks in C++ memory validator
(see logs at bottom of email), but I can't find what is wrong with my
code (if anything).
14 matches
Mail list logo
