From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32365 invoked by alias); 7 Jun 2006 03:23:11 -0000 Received: (qmail 32201 invoked by uid 48); 7 Jun 2006 03:23:02 -0000 Date: Wed, 07 Jun 2006 03:28:00 -0000 Message-ID: <20060607032302.32200.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/27908] VMSecureRandom generateSeed infinite loop? (Regression) In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-06/txt/msg00758.txt.bz2 List-Id: ------- Comment #12 from pinskia at gcc dot gnu dot org 2006-06-07 03:23 ------- (In reply to comment #11) > Alright, but, it seems strange that code that worked 2 months ago is suddenly > broken due to a bug filed 6 years ago. The "Regression" status of this > particular situation and this particular code seems to get lost when calling it > a dupe. The code changed which caused PR 1305 to show its head, csm posted a workaround to the java-patches list so someone will most likely apply it. And the regression part of this bug is not lost by calling the bug as a dup because the work around was posted. Yes it is semi weird an old bug to show its head causing this regression when the library changes. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27908