Note that in most cases threads other than the one calling `pthread_detach()` can terminate at anytime. After a call `pthread_detach()`, if the thread terminates, its resources are freed automatically, rendering the `pthread_t` no longer valid. It is impossible to tell whether a `pthread_t` is designating a thread that has terminated. It may even be designating a thread that is different from the one the user expects because thread IDs can be reused. By calling `pthread_detach()` on a `pthread_t` you _semantically_ destroy/close it and should not use it any more.
------------------ Best regards, lh_mouse 2016-06-01 ------------------------------------------------------------- 发件人："Burkhardt, Glenn B UTAS" <[email protected]> 发送日期：2016-05-31 23:11 收件人：[email protected] 抄送： 主题：[Mingw-w64-public] winpthreads, pthread_setschedparam, and detached threads The way the winpthreads code is writing, the Windows handle for the thread is cleared when the thread is made detached. That means that the pthread_setschedparam() call can't work. So thread priorities for detached threads can only be set once, at thread creation, before the thread is detached, or as part of the pthread_create() call. Is there a reason for this? For me, it's unexpected behavior. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
