From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20374 invoked by alias); 6 Jun 2006 06:42:08 -0000 Received: (qmail 20216 invoked by uid 48); 6 Jun 2006 06:42:00 -0000 Date: Tue, 06 Jun 2006 06:48:00 -0000 Message-ID: <20060606064200.20215.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libgcj/27908] VMSecureRandom generateSeed infinite loop? (Regression) In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "csm at 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/msg00648.txt.bz2 List-Id: ------- Comment #1 from csm at gnu dot org 2006-06-06 06:42 ------- This is apparently caused by the default implementation of VMSecureRandom, which uses some threads concurrently modifying counters, and uses those counters to construct random bytes. It's odd that on GCJ this runs so slow; using the jamvm interpreter I didn't notice that much of a lag (on a fast machine, sure, but I wouldn't think that on any reasonably modern machine someone would get bothered enough to file a bug). -- csm at gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |csm at gnu dot org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-06-06 06:42:00 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27908