Stas Bekman wrote: [snip]
Alternatively one could use a manager thread that implements something like a thread-specific alarm(), where a signal handler running on the interrupted thread does siglongjmp() to break out of the interrupted processing, but implementing that sort of service is not trivial.
Is it actually worth mentioning that? It seems to invite people who don't really know what they're doing around threads to get in too deep. I would imagine that anyone who's competent to do that would have already got the message from the previous text :)
