| delorie.com/archives/browse.cgi | search |
Ralf Habacker wrote: > There is only one case where I still believe that there may be a problem. > If a pthread_mutexattr_t is constructed on the stack and the magic class > membere is be exactly the predefined value, pthread_mutexattr_init() > will return EBUSY, although there is no good object, it is only by random. I believe this has been hashed out on the list before as well. I think the conclusion is that the app needs to check the return values so that it can cope with this case. I don't have a link to the thread handy. > My currently conclusion is that there are rare conditions in the pthread > and/or exception stuff, which corrupts the stack and that there is more > work required to find out the problem. This I don't doubt, but I think it will just require someone digging in. If you can whittle down the qt3 stack overflow crash to a testcase, then there's a good chance someone reading will give it more attention. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |