Thank you for checking this.
If I read this right, the leaking that was coming from the exceptions
during static linking was eliminated using this patch. That seems like a
good thing.
There are 2 leaks left, but they are always leaking. I know one of them
is argv[0] (the currently running pro
Hi,
Builds of MinGW-W64 based on GCC-4.9.1 is updated.
MinGW-w64 is updated to c6f0d3d981c70ad31bb1c2bfc2850b827281e189
GDB is updated to 7.8.1
Links:
32-bit:
posix-sjlj:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/th
I have applied the patch and here are test results:
/// using original mingw-w64 shared libs - 2 leaked
///
E:\Desktop>g++ test.cpp -std=c++11
E:\Desktop>a
++exception caught, e = 12345
/// using original mingw-w64 static libs - a nu
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,
Microsoft documents _mkdir() in
http://msdn.microsoft.com/en-us/library/2fkk4dzw.aspx
for Visual C++ 2005-2013. Maybe it was different before.
2014-10-31 22:04 GMT+02:00 Greg Jung :
> So they are in direct.h ... they used to be found in io.h, as you would
> get using MSVC, I presume.
>
> S
So they are in direct.h ... they used to be found in io.h, as you would get
using MSVC, I presume.
So why doesn't io.h #include .. should it?
hmm .. direc.h and io.h should have been included under the following from
filefn.h, which feeds filefn.cpp:
#if defined(__WINDOWS__) && !defined(__WXMI
---
mingw-w64-headers/include/winnt.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/mingw-w64-headers/include/winnt.h b/mingw-w64-headers/include/winnt.h
index a20c884..b703125 100644
--- a/mingw-w64-headers/include/winnt.h
+++ b/mingw-w64-headers/include/winnt.h
@@ -1746,6 +1746,12 @
