Re: [Mingw-w64-public] Application crashes with access violation on use std::this_thread::yield()

[xunxun]

于 2011/12/2 5:03, niXman 写道:
 Hi guys!

 When I use std::this_thread::yield(), application crashes with access 
 violation.
 If I repace __gthread_yield() in this function with sched_yield()
 everything works fine.

 Any ideas?

 Regards.
It's very strange.
Before I change it, it also crashes.
After I modify gthr-default.h,
replace return __gthrw_(sched_yield) (); with return sched_yield();
save it.

The crash is gone ...

But I think __gthrw_(sched_yield) is the same as sched_yield

-- 
Best Regards,
xunxun


--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

[Mingw-w64-public] Application crashes with access violation on use std::this_thread::yield()

[niXman]

Hi guys!

When I use std::this_thread::yield(), application crashes with access violation.
If I repace __gthread_yield() in this function with sched_yield()
everything works fine.

Any ideas?

Regards.

--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public