Subject line says it all... If you use pth, calls like select(), sleep(), and usleep() are not interrupted by non-blocked signals. This would seem to be at odds with Posix behavior, or at least, it is not consistent with Linux/glibc2 behavior. As an example: I have added pth support to Python. If I invoke time.sleep(n) interactively, and then try to interrupt with control-C, nothing happens until n seconds elapse, and then the interrupt is processed. I've worked up a patch for this against 1.3.7, which adds the signal set to the event ring in various places. It seems to fix the immediate problem. Do we agree this is an actual bug? If so, I'll send the patch. It doesn't break the pth tests. -- andy dustman | programmer/analyst | comstar.net, inc. telephone: 770.485.6025 / 706.549.7689 | icq: 32922760 | pgp: 0xc72f3f1d "Therefore, sweet knights, if you may doubt your strength or courage, come no further, for death awaits you all, with nasty, big, pointy teeth!" ______________________________________________________________________ GNU Portable Threads (Pth) http://www.gnu.org/software/pth/ User Support Mailing List [EMAIL PROTECTED] Automated List Manager (Majordomo) [EMAIL PROTECTED]
