public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/9947: gcj run into segmentation fault when compiling JAR files
Date: Mon, 10 Mar 2003 18:26:00 -0000	[thread overview]
Message-ID: <20030310182601.27719.qmail@sources.redhat.com> (raw)

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

From: Tom Tromey <tromey@redhat.com>
To: jfey@stratus.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/9947: gcj run into segmentation fault when compiling JAR files
Date: 10 Mar 2003 11:12:51 -0700

 >>>>> "Julia" == jfey  <jfey@stratus.com> writes:
 
 >> Number:         9947
 >> Category:       java
 
 Julia> When executing the following command line, gcj generates 
 Julia> segmentation fault:
 Julia> gcj -o TestGetInap --main=TestGetInap asn.jar asn1rt.jar JainInapApi1.0.jar inap.jar sinap.jar libsinap_jni.so
 Julia> com/objsys/asn1j/runtime/Asn18BitCharString.java:0: internal error: Segmentation Fault
 Julia> Please submit a full bug report,
 Julia> with preprocessed source if appropriate.
 Julia> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 Julia> The asn1rt.jar file is a 3rd party JAR come with ASN1
 Julia> compiler. Some of the logging class (Logger) are not
 Julia> implemented.
 
 Is it 3rd party free software, or 3rd party proprietary software.
 If the latter, don't send it.
 
 I won't have time to look at this in the near future.  However:
 
 * If you run `gcj -v ...' you can see the command line for jc1.  If
   you run this under the debugger you can get a stack trace.  That
   might help.
 
 * gcj 3.3 is due out soon.  This has a lot of bug fixes.  You could
   try building it and seeing if it helps.
 
 Tom


             reply	other threads:[~2003-03-10 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 18:26 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-04 21:06 jfey

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=20030310182601.27719.qmail@sources.redhat.com \
    --to=tromey@redhat.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).