[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ack of bug submission?

From: Bobby Krupczak
Subject: ack of bug submission?
Date: Mon, 22 Apr 2002 11:50:00 -0400 (EDT)


Is there any acknowledgment mechanism for bugs that have been
submitted?  We sent in this email message last week and have not
received any reply.



>We think we have encountered this same bug with glibc on RH 6, 7, 7.1
>kernels 2.2.x and 2.4.x and glibc
>evil.empire.com%uname -a
>Linux evil.empire.com 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 i686 unknown
>evil.empire.com%rpm -qa | grep glibc
>zapdos%uname -a
>Linux zapdos 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown
>zapdos%rpm -qa | grep -i glib
>evil.empire.com%ldd collector.exe
>         libc.so.6 => /lib/libc.so.6 (0x4001a000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>zapdos%ldd ./collector.exe
>         libc.so.6 => /lib/i686/libc.so.6 (0x40021000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>Basically, we are doing something similar.  We are using SIGALRM to 
>break out of various socket and other system calls.  If we block on 
>connect(), we catch SIGALRM but then seem to go back into connect and 
>sleep for a long long time before it occassionally resumes.
>Has this bug been fixed in subsequent glibc releases?  My ass hurts from 
>all the buckshot I've taken over this potential bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]