public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: steve <steve@netfuel.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libgcj/10214: VM fails to init.
Date: Wed, 26 Mar 2003 15:18:00 -0000	[thread overview]
Message-ID: <20030326145601.16830.qmail@sources.redhat.com> (raw)

The following reply was made to PR libgcj/10214; it has been noted by GNATS.

From: steve <steve@netfuel.com>
To: tromey@redhat.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/10214: VM fails to init.
Date: Wed, 26 Mar 2003 08:52:25 -0600

 GNU ld version 2.11.93.0.2 20020207
 
 Tom Tromey wrote:
 >>>>>>"steve" == steve  <steve@netfuel.com> writes:
 >>>>>
 > 
 >>>Number:         10214
 >>>Category:       libgcj
 >>>Synopsis:       VM fails to init.
 >>
 > 
 >>>gij HelloWorld 
 >>>#0  0x0009015f in ?? ()
 >>>#1  0x4038b5f2 in _Jv_Throw (value=0x808dfa0) at ../../../libjava/exception.cc:100
 >>>#2  0x4039c8c5 in java::lang::Class::forName(java::lang::String*, bool, java::lang::ClassLoader*) (className=0x80998c0,
 >>>    initialize=1 '\001', loader=0x80abfc0) at ../../../libjava/java/lang/natClass.cc:83
 >>>#3  0x4039c98a in java::lang::Class::forName(java::lang::String*) (className=0x4a415641) at ../../../libjava/java/lang/natClass.cc:110
 >>>#4  0x40366a9a in gnu.gcj.convert.UnicodeToBytes.getDefaultEncoder() () at ../../../libjava/gnu/gcj/convert/UnicodeToBytes.java:49
 >>
 > 
 > 
 > This is probably the first exception thrown during library startup.
 > Given that, and given that we're crashing during the throw, I suspect
 > you need a different (more recent) linker.  What linker are you using?
 > 
 > Tom
 > 
 
 


             reply	other threads:[~2003-03-26 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 15:18 steve [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-28 20:06 Tom Tromey
2003-03-28 18:56 steve
2003-03-27 23:24 Tom Tromey
2003-03-26 17:26 steve
2003-03-25 23:37 Tom Tromey
2003-03-25 22:46 steve

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=20030326145601.16830.qmail@sources.redhat.com \
    --to=steve@netfuel.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).