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 this lock, hence its
memory leaks.
--
Best regards,
lh_mouse
2014-09-28
The simplified version of the test looks like this:
#include
#include
void* tmp_thr(void *p) {
printf("%d\n", *(int*)p);
}
int main() {
int j;
for(j=0;j<80;j++) {
pthread_t t;
pthread_create(&t, NULL, tmp_thr, &j);
p
hey
in the mingw-w64 version i have (installed by win-builds 1.4),
localtime_r() is guarded by _POSIX (see time.h), so any program that
uses localtime_r has to pass -D_POSIX.
jony mentioned on IRC that, as guards were removed for strtok_r(),
maybe it should also be the case for localtime_r.
also
Loïc Le Cunff писал 2014-09-28 05:06:
> Greetings,
>
> This is an issue that I've had for a while actually as I had it in
> TDM-GCC one year ago.
>
> Now, since TDM-GCC appears to be based on MinGW-w64's winpthread, I
> tried going back to the source hoping for a fix, and so I installed
> MinGW-w
Greetings,
This is an issue that I've had for a while actually as I had it in
TDM-GCC one year ago.
Now, since TDM-GCC appears to be based on MinGW-w64's winpthread, I
tried going back to the source hoping for a fix, and so I installed
MinGW-w64 based on gcc 4.9.1 for x86_64, using posix threa
just got this from O'reilly.com, it's a security alert.
as you know, MSYS uses BASH and so does cygwin.
Forwarded Message
Subject: Programming Today: Bash shellshock, Python 3, peer code review
+ more
Date: Sat, 27 Sep 2014 06:10:26 -0700
From: O'Reilly Media
To: jm
Yes, that is an unusual case. We could introduce an header to
redefine all UNICODE-depedent macros based on current state ... but
not sure if that would be worth the effort. So yes, patch is ok.
Thanks,
Kai
--
Meet PCI
Patch is fine. Please apply.
Thanks,
Kai
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Com
Hi Jacek,
patch is ok. Please apply.
Thanks,
Kai
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DS
