This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug java/16653] incompatible type on stack
- From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 21 Jul 2004 07:25:16 -0000
- Subject: [Bug java/16653] incompatible type on stack
- References: <20040721062243.16653.mwteng@hotmail.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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