I have also been seeing this scheduler error. I traced my problem down to the way select is handled. The select event remains in force until it is satisfied or the timeout expires. If during this period, one of the selectable file descriptors is closed, say, the select in pth_sched_eventmanager will fail (EBADFD) on the platform I am using. This has the result of looping around in pth_sched with the run queue empty, generating the observed failure. Your problem may be similar is nature. To remedy the problem, I rewrote a small amount of the user code. Clearly, is is possible to "fix" this in pth but there is more than one solution available and it is not clear which, if any, should be adopted.
Hope this helps [EMAIL PROTECTED] wrote: >I got a message when I called pth_accept function: >**Pth** SCHEDULER INTERNAL ERROR: no more thread(s) available to >schedule!?!? >and the application is down( core dumped ). > >why? >______________________________________________________________________ >GNU Portable Threads (Pth) http://www.gnu.org/software/pth/ >User Support Mailing List [EMAIL PROTECTED] >Automated List Manager (Majordomo) [EMAIL PROTECTED] > ______________________________________________________________________ GNU Portable Threads (Pth) http://www.gnu.org/software/pth/ User Support Mailing List [EMAIL PROTECTED] Automated List Manager (Majordomo) [EMAIL PROTECTED]
