public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jojelino at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/51500] [4.7 regression] 106 unexpected libjava testsuite failures with mingw32
Date: Mon, 06 Feb 2012 16:20:00 -0000	[thread overview]
Message-ID: <bug-51500-4-mi26x52ZSp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51500-4@http.gcc.gnu.org/bugzilla/>

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

gee <jojelino at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #26574|0                           |1
        is obsolete|                            |

--- Comment #24 from gee <jojelino at gmail dot com> 2012-02-06 16:18:44 UTC ---
Created attachment 26584
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26584
proposed patch for workaround TestEarlyGC failure

fixed wrong assumption to the code. but got following in ExtraClassLoader test
Starting program: /tmp/gcc/i686-pc-mingw32/libjava/.libs/gij -cp
D:\\cygwin\\tmp\\gcc\\libjava\\testsuite\\libjava.lang\\ExtraClassLoader.jar
ExtraClassLoader
[New Thread 5268.0x140c]
[New Thread 5268.0xd84]
Exception in thread "main" java.lang.SecurityException: attempt to use
uninitialized class loader
   at
java.lang.Throwable.<init>(/tmp/gcc/libjava/classpath/java/lang/Throwable.java:161)
   at
java.lang.ClassLoader.checkInitialized(/tmp/gcc/libjava/classpath/java/lang/Exception.java:78)
   at
java.lang.ClassLoader.findLoadedClass(/tmp/gcc/libjava/java/lang/ClassLoader.java:694)
   at
java.lang.Class.forName(/tmp/gcc/i686-pc-mingw32/libjava/../.././libjava/java/lang/natClass.cc:105)
   at ExtraClassLoader.main(ExtraClassLoader.java:8)
[Inferior 1 (process 5268) exited with code 01]
(gdb)


  parent reply	other threads:[~2012-02-06 16:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 18:59 [Bug libgcj/51500] New: " jojelino at gmail dot com
2011-12-10 19:19 ` [Bug libgcj/51500] " jojelino at gmail dot com
2011-12-12 10:13 ` rguenth at gcc dot gnu.org
2011-12-12 14:49 ` jojelino at gmail dot com
2011-12-12 14:51 ` jojelino at gmail dot com
2011-12-17 22:03 ` ktietz at gcc dot gnu.org
2011-12-18 22:10 ` jojelino at gmail dot com
2012-01-16 13:24 ` jojelino at gmail dot com
2012-01-18 13:57 ` jojelino at gmail dot com
2012-01-29 11:55 ` jojelino at gmail dot com
2012-01-30  9:03 ` jojelino at gmail dot com
2012-01-30  9:22 ` ktietz at gcc dot gnu.org
2012-01-30 15:53 ` jojelino at gmail dot com
2012-01-30 17:27 ` ubizjak at gmail dot com
2012-01-30 19:59 ` ktietz at gcc dot gnu.org
2012-01-30 20:30 ` ubizjak at gmail dot com
2012-01-30 23:05 ` ktietz at gcc dot gnu.org
2012-01-30 23:33 ` ubizjak at gmail dot com
2012-01-31 10:08   ` Kai Tietz
2012-01-31 10:09 ` ktietz70 at googlemail dot com
2012-02-01  5:21 ` jojelino at gmail dot com
2012-02-01 10:47 ` ktietz at gcc dot gnu.org
2012-02-04 11:32 ` jojelino at gmail dot com
2012-02-05  1:23 ` jojelino at gmail dot com
2012-02-05  2:11 ` jojelino at gmail dot com
2012-02-05  2:44 ` jojelino at gmail dot com
2012-02-06 16:20 ` jojelino at gmail dot com [this message]
2012-02-13 15:20 ` ktietz at gcc dot gnu.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-51500-4-mi26x52ZSp@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).