public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/16653] incompatible type on stack
Date: Wed, 21 Jul 2004 07:25:00 -0000	[thread overview]
Message-ID: <20040721072516.32685.qmail@sourceware.org> (raw)
In-Reply-To: <20040721062243.16653.mwteng@hotmail.com>


------- Additional Comments From rmathew at gcc dot gnu dot org  2004-07-21 07:25 -------
(In reply to comment #0)
> When try running the binary, its failed with ...
> org.apache.xercs.parsers.XML11Configuration::configureXML11Pipeline(()V):
> incompatible type on stack ...

You mean when you execute "a.out", right?

This looks like a bytecode verification error...


> The way in which the application is built are:
> (1) convert two required xml parser jar to object for linking...
>     e.g. gcj -c -O2 xmlParserAPIs.jar

This is a weird usage...you can just specify xmlParserAPIs.jar
on the next GCJ command line...


> (2) compile the application source and link with those libraries.
>     e.g. gcj -O2 --main=Main Main.java xmlParserAPIs.o xercesImpl.o
> 
> BTW, I could like to know how to submit a complete report for investigation.

You can help by running GCJ's "jcf-dump" (or JDK's "javap") on
the class "org.apache.xerces.parsers.XML11Configuration" and pasting
the output for the method "configureXML11Pipeline" - do make sure
to have the relevant JARs in your CLASSPATH when you run this. For
example (on Linux):

jcf-dump --classpath xmlParserAPIs.jar -c
org.apache.xerces.parsers.XML11Configuration >foo.txt

(Note the "-c" flag.)

Open "foo.txt" and copy the method body for "configureXML11Pipeline"
into this bug report.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


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


  parent reply	other threads:[~2004-07-21  7:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21  6:22 [Bug java/16653] New: " mwteng at hotmail dot com
2004-07-21  7:15 ` [Bug java/16653] " pinskia at gcc dot gnu dot org
2004-07-21  7:25 ` rmathew at gcc dot gnu dot org [this message]
2004-07-21  8:32 ` mwteng at hotmail dot com
2004-07-21  8:47 ` mwteng at hotmail dot com
2004-07-21 11:40 ` rmathew at gcc dot gnu dot org
2004-07-22  1:18 ` mwteng at hotmail dot com
2004-07-22  2:43 ` mwteng at hotmail dot com
2004-07-22 10:43 ` rmathew at gcc dot gnu dot org
2004-07-22 13:30 ` mwteng at hotmail dot com
2004-07-23  2:08 ` mwteng at hotmail dot com
     [not found] <bug-16653-8958@http.gcc.gnu.org/bugzilla/>
2006-02-06 21:54 ` tromey 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=20040721072516.32685.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).