Bug#374834: I think this is a known bug in libc

2006-11-13 Thread Tim Dijkstra
On Sat, 11 Nov 2006 18:28:13 +0100 <[EMAIL PROTECTED]> wrote: > On Wed, Oct 25, 2006 at 02:13:04PM +0200, Tim Dijkstra wrote: > > Hi, > > > > I think this related to the following bug report to libc. Symptoms are > > really the same apart from the fact that update-menu doesn't use > > signals...

Bug#374834: I think this is a known bug in libc

2006-11-11 Thread Mario 'BitKoenig' Holbe
On Sat, Nov 11, 2006 at 06:28:13PM +0100, [EMAIL PROTECTED] wrote: > Are you using SMP hardware ? The locking code has not changed since Well, I don't use SMP hardware on the problematic machine. Even more than that: it does only appear on some machines, on others I have never observed this. And a

Bug#374834: I think this is a known bug in libc

2006-11-11 Thread allomber
On Wed, Oct 25, 2006 at 02:13:04PM +0200, Tim Dijkstra wrote: > Hi, > > I think this related to the following bug report to libc. Symptoms are > really the same apart from the fact that update-menu doesn't use > signals... > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223110 > > See also

Bug#374834: I think this is a known bug in libc

2006-10-25 Thread Tim Dijkstra
Hi, I think this related to the following bug report to libc. Symptoms are really the same apart from the fact that update-menu doesn't use signals... http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223110 See also red hat bug linked from the libc report, where there is a test case with a deadl