Thanh Luu wrote:
> The problem is pth doesn't handle errors correctly during select (actually,
> it ignores errors) and wait on fd events. When an error such as EINVAL or
> EBADF occurs, pth ignores it, which eventually leads to the thread never
> being reawaked and no threads being scheduled. The patch will go through
Seems like this patch is closer to the "right" thing to do in the case of
a bad file descriptor, which is to have pth_read() (or whatever) return
in exactly the same way that read() (or whatever) would, i.e., return -1
and set errno to EBADF.
I've learned that "no threads to schedule?!?" is often pth code language
for "you closed one of my file descriptors dummy!!"
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
