| … | |
… | |
| 5 | Glibc contains a bug that causes any program linked against pthreads AND |
5 | Glibc contains a bug that causes any program linked against pthreads AND |
| 6 | using coroutines (of any kind, not only Coro, but including most userspace |
6 | using coroutines (of any kind, not only Coro, but including most userspace |
| 7 | thread libraries like gnu-pth) or alternate stacks to segfault on calls to |
7 | thread libraries like gnu-pth) or alternate stacks to segfault on calls to |
| 8 | pthread functions. And glibc happens to do a lot of these calls. |
8 | pthread functions. And glibc happens to do a lot of these calls. |
| 9 | |
9 | |
| 10 | (Even if you perl is not compiled against pthreads, Time::HiRes links |
10 | (Even if your perl is not compiled against pthreads, e.g. Time::HiRes links |
| 11 | against -lrt, which drags in pthreads. The same is true for other modules, |
11 | against -lrt, which drags in pthreads. The same is true for other modules, |
| 12 | so watch out). |
12 | so watch out). |
| 13 | |
13 | |
| 14 | The bug is rather difficult to fix. This is not a problem, however, since |
14 | The bug is rather difficult to fix. This is not a problem, however, since |
| 15 | glibcs compiled for linux-2.4 use a much more efficient method to locate |
15 | glibcs compiled for linux-2.4 use a much more efficient method to locate |
