Yes, this is a known glibc bug: http://bugs.debian.org/208428 . You could have determined that by looking at http://bugs.debian.org/libc6 ; this one's right at the top. (No idea when they'll fix it, sorry.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger amu@monk.mit.edu (NOT a valid e-mail address) for more info.