public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: doparsons@rev.net
To: gcc-gnats@gcc.gnu.org
Subject: libgcj/9608: compiled  VS gij virtual machine
Date: Fri, 07 Feb 2003 01:06:00 -0000	[thread overview]
Message-ID: <20030207010139.21849.qmail@sources.redhat.com> (raw)


>Number:         9608
>Category:       libgcj
>Synopsis:       compiled  VS gij virtual machine
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 07 01:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Doug Parsons
>Release:        gcc 3.2.2 debian unstable package
>Organization:
>Environment:
Linux Debian Potato 2.2 i586 200 mmx
>Description:
What would cause the failure of a static compiled java program that runs without errors in the gij virtual machine or when compiled dynamic? 

The compile process produces no errors and only warnings with -Wall. Two areas that are currently affecting the runtime are:

Exception in thread "main" java.lang.RuntimeException: The SHA algorithm was not found to use in computing the Serial Version UID for class Pyramid.Settings

When trying to write to disk.  And:

Exception in thread "main" class java.lang.ExceptionInInitializerError: java.util.MissingResourceException: Bundle gnu.java.locale.Calendar not found

This package does not seem to be in the gnu library. But why does it not fail in the VM but does when compiled static?

I ask this in a general manner because this is new to me and to give further details it would help to know what to look for if hunting a possible bug.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-02-07  1:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030207010139.21849.qmail@sources.redhat.com \
    --to=doparsons@rev.net \
    --cc=gcc-gnats@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).