Bug#205099: Please check these bugs with the latest glibc

To: 205099-submitter@bugs.debian.org, 205099@bugs.debian.org, Anthony DeRobertis <asd@suespammers.org>, 205234-submitter@bugs.debian.org, 205234@bugs.debian.org, Juergen Kreileder <jk@blackdown.de>, 211621-submitter@bugs.debian.org, 211621@bugs.debian.org
Subject: Bug#205099: Please check these bugs with the latest glibc
From: GOTO Masanori <gotom@debian.or.jp>
Date: Tue, 04 Nov 2003 00:16:22 +0900
Message-id: <[🔎] 80y8ux8ou1.wl@oris.opensource.jp>
Reply-to: GOTO Masanori <gotom@debian.or.jp>, 205099@bugs.debian.org

Hi all,

Bug#205099, #205234, and #211621 have sit as Grave bug for 2 or 3
months - but at last any developers can't reproduce this problem.  I
doubt they're really long-standing grave bug because more other
reporters have not reported.  Please check these bugs with the latest
glibc (it's good idea to run on both 2.4 and 2.6 kernels).

Regards,
-- gotom

Reply to:

Prev by Date: Bug#209139: marked as done (rpc.mountd 1.0.5 requires restarting to avoid crashes with glibc 2.3.2)
Next by Date: Bug#216921: The Problem exists in other programms too
Previous by thread: Bug#209139: marked as done (rpc.mountd 1.0.5 requires restarting to avoid crashes with glibc 2.3.2)
Next by thread: Bug#211621: Please check these bugs with the latest glibc
Index(es):
- Date
- Thread