Re: [Mingw-w64-public] std::thread and memory leaks

2015-04-22 Thread Yaron Keren
stderr is not likely to show up anywhere with a GUI program. The standard practice in Windows is to use OutputDebugString. https://msdn.microsoft.com/en-us/library/windows/desktop/aa363362%28v=vs.85%29.aspx 2015-04-22 14:15 GMT+03:00 LRN : > On 22.04.2015 14:02, Óscar Fuentes wrote: > > LRN wri

Re: [Mingw-w64-public] std::thread and memory leaks

2015-04-22 Thread LRN
On 22.04.2015 14:02, Óscar Fuentes wrote: > LRN writes: > >> Here's a patch to fix this. >> It does solve the problem for the simple testcase, but i have no idea how it >> would behave in the wild, i didn't test it on anything else. One might notice >> that it is set to crash when certain things h

Re: [Mingw-w64-public] std::thread and memory leaks

2015-04-22 Thread Óscar Fuentes
LRN writes: > Here's a patch to fix this. > It does solve the problem for the simple testcase, but i have no idea how it > would behave in the wild, i didn't test it on anything else. One might notice > that it is set to crash when certain things happen. I'm not sure whether these > things would

Re: [Mingw-w64-public] std::thread and memory leaks

2015-04-22 Thread LRN
On 02.10.2014 10:03, niXman wrote: > JonY 2014-10-02 02:11: >> On 9/28/2014 14:44, lh_mouse wrote: >>> mingw-w64-libraries/winpthread/src/spinlock.c:66 >>> int initrv = pthread_spin_init (lock, >>> PTHREAD_PROCESS_PRIVATE); >>> >>> There is no corresponding pthread_spin_destroy() for thi