Some more data points. On the same machine, running Linux 2.6.32-3-amd64 (from Debian)
- I cannot reproduce the problem from comment #13 in a sid chroot
- I can reproduce the problem in a lucid chroot
- I can reproduce the problem in a sid chroot, using the libc packages from Debian experimental (2.11.0)
So it is clearly either a libc bug, or a bug in ruby triggered by a change in libc.
Some more data points. On the same machine, running Linux 2.6.32-3-amd64 (from Debian)
- I cannot reproduce the problem from comment #13 in a sid chroot
- I can reproduce the problem in a lucid chroot
- I can reproduce the problem in a sid chroot, using the libc packages from Debian experimental (2.11.0)
So it is clearly either a libc bug, or a bug in ruby triggered by a change in libc.