AFAIK mingw-w64 uses callbacks to reclaim TLS memory. In the first
case, upon destruction of the static object there were 5 blocks of
memory unfreed; and in the second case there were 6. If we say there
was no memory leak in case 1, then there must be in case 2, IMO.
I've tried this myself,
Hi guys:
I got memory leaks in this code. Hope someone would help.
Minimal sample code attached.
Compiled with g++ test.cpp -std=c++11 -static, then attached with OllyDbg, bp
malloc, calloc, realloc, free. There were 2 or 3 blocks of memory that were not
freed upon termination.
gcc -v:
Thread
Hello
lh_mouse lh_mo...@126.com schrieb am 18:38 Donnerstag, 16.Januar 2014:
I got memory leaks in this code. Hope someone would help.
Minimal sample code attached.
Compiled with g++ test.cpp -std=c++11 -static, then attached with OllyDbg, bp
malloc, calloc, realloc, free. There were 2 or
-
发件人：Hannes Domani ssb...@yahoo.de
发送时间：2014-01-17 05:34
主题：Re: [Mingw-w64-public] Potential memory leaks in exception handling?
收件人：mingw-w64-public@lists.sourceforge.netmingw-w64-public@lists.sourceforge.net
抄送：
Hello
lh_mouse lh_mo...@126.com schrieb am 18:38 Donnerstag, 16.Januar 2014:
I
Additional information:
Another example attached.
On line #54 there is an #if directive. If I put an #if 0 there, the function
ThreadProc() would get directly called - hence would run in the same thread
with main() - and I got the following result:
E:\Desktopg++ test2.cpp -static -std=c++11
AFAIK mingw-w64 uses callbacks to reclaim TLS memory. In the first case, upon
destruction of the static object there were 5 blocks of memory unfreed; and
in the second case there were 6. If we say there was no memory leak in case
1, then there must be in case 2, IMO.
I've tried this
