Bug#657810: and

2012-01-29 Thread Robert Millan
El 29 de gener de 2012 12:39, Petr Salinger ha escrit: > No, the   have to be part of eglibc, > you can silently break ABI, by changing errno.h. Ok. I'll resync both files manually then. > In fact, due to changes of ELAST it just happened, How do you increase ELAST then? Currently we need to i

Bug#657810: and

2012-01-29 Thread Petr Salinger
kfreebsd-kernel-headers 0.70 includes properly patched versions of and which could be used to compile glibc. Please consider using those instead of the in-tree copies. A patch for is attached. can be used directly. No, the have to be part of eglibc, you can silently break ABI, by changing

Bug#657835: libc6: libc deadlocks in child process after fork

2012-01-29 Thread Aurelien Jarno
On Sun, Jan 29, 2012 at 02:09:06PM +0400, Max Dmitrichenko wrote: > Package: libc6 > Version: 2.11.3-2 > Severity: important > > One thread of multithreaded application calls fork(). According to the POSIX > standard only that thread which called fork() would present in the child > process. But th

Bug#657835: libc6: libc deadlocks in child process after fork

2012-01-29 Thread Max Dmitrichenko
This is the stack trace of a deadlocked child: #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x00346929c08d in _L_lock_2164 () at tzset.c:138 #2 0x00346929be47 in __tz_convert (timer=0x346959da74, use_localtime=0, tp=0x7f7a25211990) at tzse

Bug#657835: libc6: libc deadlocks in child process after fork

2012-01-29 Thread Max Dmitrichenko
Package: libc6 Version: 2.11.3-2 Severity: important One thread of multithreaded application calls fork(). According to the POSIX standard only that thread which called fork() would present in the child process. But the state of all mutexes, condvars and other objects are copied into the child pro