public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "r_ovidius at eml dot cc" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/27908]  New: VMSecureRandom generateSeed infinite loop? (Regression)
Date: Tue, 06 Jun 2006 04:11:00 -0000	[thread overview]
Message-ID: <bug-27908-7936@http.gcc.gnu.org/bugzilla/> (raw)

gcc version 4.2.0 20060605 (experimental)

I'm trying to run jsch (jcraft.com) with the examples/PortForwardingR.java and
id_dsa identity.  It worked before the most recent classpath import (works in
gcj 20060420), but now it just results in an infinite loop and a pegged cpu.

My guess is that it spins forever in the SecureRandom call to
VMSecureRandom.generateSeed.  This class didn't exist in 20060420 but jsch
worked fine.

I'm not sure if it is classpath or bad code generation in gcj causing the
infinite loop.

This testcase pegs the cpu.  Works fine with Sun's java.
---
import java.security.*;
public class GR {
  public static void main(String[] a) {
    SecureRandom sr = new SecureRandom();
    byte[] ba = sr.getSeed(5);
    System.err.println(ba);
  } 
}


-- 
           Summary: VMSecureRandom generateSeed infinite loop? (Regression)
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: r_ovidius at eml dot cc


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27908


             reply	other threads:[~2006-06-06  4:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  4:11 r_ovidius at eml dot cc [this message]
2006-06-06  4:34 ` [Bug libgcj/27908] " pinskia at gcc dot gnu dot org
2006-06-06  6:42 ` csm at gnu dot org
2006-06-06 20:07 ` csm at gnu dot org
2006-06-06 20:14 ` csm at gnu dot org
2006-06-06 20:21 ` r_ovidius at eml dot cc
2006-06-06 21:29 ` csm at gnu dot org
2006-06-06 21:30 ` csm at gnu dot org
2006-06-06 21:32 ` [Bug java/27908] " csm at gnu dot org
2006-06-07  0:08 ` csm at gnu dot org
2006-06-07  0:14 ` pinskia at gcc dot gnu dot org
2006-06-07  2:52 ` csm at gnu dot org
2006-06-07  3:16 ` r_ovidius at eml dot cc
2006-06-07  3:23 ` pinskia at gcc dot gnu dot org
2006-06-07  4:49 ` csm at gnu dot org
2006-06-13 12:44 ` aph at gcc dot gnu dot org
2006-06-19 17:38 ` aph at gcc dot gnu dot org
2007-09-04 14:00 ` aph at gcc dot gnu dot org
2007-09-04 17:55 ` aph at gcc dot gnu dot org
2007-09-04 17:58 ` aph at gcc dot gnu dot org
2007-09-04 18:01 ` aph at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27908-7936@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).