[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [aspectj-users] Invalid byte tag in constant pool: 105
|
Hi Torsten,
As an end user you should never see
a failure like that - so this is a bug. I've had a quick look through
existing bugs we know about in bugzilla but can't find anything similar
to this one.
Just before I ask you to raise a bug
... can you possibly try this using the latest development version of AspectJ?
It has many many bug fixes and a new level of the JDT compiler inside.
It also includes some basic dump support so that when the compiler
fails with an ABORT it should produce an 'ajcore' file that contains diagnostic
information that we can hopefully use to fix the problem. The latest
builds of AspectJ are always available here:
http://download.eclipse.org/technology/ajdt/dev/aspectj-DEVELOPMENT.jar
Looking at the stack trace you have
included, it appears you are failing before we do any weaving which suggests
it *could* be a JDT compiler issue - so it is definetly worth trying the
latest aspectj development build that has the Eclipse 3.0 final version
of the compiler inside.
Anyway - assuming that it does still
fail, can I ask you to raise a bug for this in the bugzilla database? (
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ )
We can fix this faster if we have these
kinds of information in the report:
- An ajcore file if the compiler crashed
(it will de stamped with a date and time and when the crash occurs you
should be told where it has been put in the filesystem)
- Some information on how you were using
AspectJ. Binary weaving? Using intertype declarations?
- Ideally some source code that demonstrates
the failure, if you are able to distill it down to a small enough sample.
many thanks,
Andy.
---
Andy Clement
AspectJ/AJDT Committer
"Torsten Lull"
<Torsten.Lull@xxxxxxx>
Sent by: aspectj-users-admin@xxxxxxxxxxx
02/09/2004 07:40
Please respond to
aspectj-users@xxxxxxxxxxx |
|
To
| <aspectj-users@xxxxxxxxxxx>
|
cc
|
|
Subject
| [aspectj-users] Invalid byte tag in
constant pool: 105 |
|
Hello,
I'm not aware what has changed in my environment. But the compiler is no
longer willing to run. With the verbose option it produces the following
output:
zipfile classpath entry does not exist: i:\java\jdk142\jre\lib\i18n.jar
directory classpath entry does not exist:
i:\java\jdk142\jre\classes
ABORT
Exception thrown from AspectJ 1.2
This might be logged as a bug already -- find
current bugs at
http://bugs.eclipse.org/bugs/buglist.cgi?product=AspectJ&component=Compiler
Bugs for exceptions thrown have titles File:line
from the top stack,
e.g., "SomeFile.java:243"
If you don't find the exception below in a
bug, please add a new bug
at http://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ
To make the bug a priority, please include a test program
that can reproduce this exception.
Invalid byte tag in constant pool: 105
Invalid byte tag in constant pool: 105
org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
pool: 105
at org.apache.bcel.classfile.Constant.readConstant(Constant.java:145)
at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:103)
at org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:254)
at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:162)
at org.aspectj.weaver.bcel.Utility.makeJavaClass(Utility.java:358)
at org.aspectj.weaver.bcel.UnwovenClassFile.getJavaClass(UnwovenClassFile.java:63)
at org.aspectj.weaver.bcel.BcelWeaver.addClassFile(BcelWeaver.java:270)
at org.aspectj.weaver.bcel.BcelWeaver.addClassFile(BcelWeaver.java:285)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.initBcelWorld(AjBuildManager.java:455)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:143)
at org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:94)
at org.aspectj.ajdt.ajc.AjdtCommand.doCommand(AjdtCommand.java:102)
at org.aspectj.ajdt.ajc.AjdtCommand.runCommand(AjdtCommand.java:53)
at org.aspectj.tools.ajc.Main.run(Main.java:280)
at org.aspectj.tools.ajc.Main.runMain(Main.java:217)
at org.aspectj.tools.ajc.Main.main(Main.java:79)
1 fail|abort
Signal 127
Has anyone an idea, what happened????
Thanks in advance
Torsten