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



------- Comment #5 from csm at gnu dot org  2006-06-06 21:29 -------
On futher inspection, it is pegging my CPU as well. `top' was lying to me.

It *looks* as though the test `while (running)' may have been optimized away,
because the threads continue to run even after the `running' variable has been
set to false.

The attached test case seems to illustrate the problem, and it looks like a GCJ
bug. This test case:

  - Fails to exit when compiled with GCJ 20060606. Command line: gcj -g -O2 -o
PR27908 
  - Fails to run interpreted when compiled with 'gcj -C'. Error is
'java.lang.IllegalAccessError: PR27908: PR27908$run1.stop()V'.
  - Fails to run on Sun Java 1.5.0_03 on GNU/Linux x86 if compiled with 'gcj
-C'. Error is 'java.lang.VerifyError: (class: PR27908, method: main signature:
([Ljava/lang/String;)V) Illegal use of nonvirtual function call'.
  - Fails to run on jamvm if compiled 'gcj -C'. Error is similar to that on
gij: an IllegalAccessError.

This test case runs fine if compiled with Sun's 'javac -source 1.4 -target 1.4'
on both gij, java, and jamvm.


-- 


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


  parent reply	other threads:[~2006-06-06 21:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  4:11 [Bug libgcj/27908] New: " r_ovidius at eml dot cc
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 [this message]
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=20060606212911.18907.qmail@sourceware.org \
    --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).