#39 IllegalStateException:CONSTANT_info: invalid tag value [60]

[sandy]

I've a huge set of jars running to hundreds of them and
thousands of classes in them. When running with ant
1.6.2 on Linux having 8GB RAM, and max heap size of
JVM set to -Xmx1024m.
I get the following exception
java.lang.IllegalStateException: CONSTANT_info: invalid
tag value [60]
This happens while the instrumentation path is being
processed.

Any pointers?

I have not done my research yet, but thought would get
a quick help.

-Sandy

By: Nobody/Anonymous - nobody
RE: java.lang.IllegalStateException:
2005-06-15 13:23
This has never come up before. Could you create a new
bug issue in the tracker with the following info:

- version of EMMA being used
- version of Java compiler you are using (are you
compiling the offending class yourself?)
- isolate the offending jar or .class file and attach it to
the issue

Vlad,

By: Nobody/Anonymous - nobody
RE: java.lang.IllegalStateException:
2005-06-16 01:07
The "Bugs" and the "Tracker" links are not showing up

FYI
Emma version - EMMA v2.0.4217

%>java -version
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition
(build 1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed
mode) (The classes are pre-compiled, not sure which
version of jdk has been used)

For the last item, I may not be able to attach the class
file as I would need to take permission for that. Could I
assume that the last class name displayed while
parsing the instrumentation path is the offending class?

-Sandy

By: Vlad Roubtsov - vlad_r
RE: java.lang.IllegalStateException:
2005-06-16 06:15
>The "Bugs" and the "Tracker" links are not showing
up

Please go to EMMA's SourceForge project page.
Nobody else seems to have trouble finding the bug
tracker.

>For the last item, I may not be able to attach the class
file as I would need to take permission for that.

Well, as far as I am concerned there is no problem if I
don't have the data to reproduce it. So, help me help
you.

>Could I assume that the last class name displayed
while parsing the instrumentation path is the offending
class?

With what verbosity level? I would set it to "trace1". You
could alway isolate the class and reproduce the
problem via a dedicated instrumentation path so you
don't always have to re-instrument your huge jar set.

Let's continue this discussion in the appropriate bug
tracker thread.

Vlad.

--

I excluded the trouble making jars from the
instrumentation path, and got through the
instrumentation phase.

-Sandy

[Vlad Roubtsov]

Logged In: YES
user_id=1013207

Ostensibly, this is a problem in bytecode parsing code that
is more than 4 years old and has not had any issues for
hundreds of users.

I can think of these reasons right now:

(1) you are using a Java 1.5 compiler and there are some
.class format changes EMMA is not aware of. That can't be
it, because you told me you are using JDK 1.4

(2) you are using a bytecode enhancer (JDO, AspectJ, etc)
prior to EMMA instrumentation. You need to let me know if
this is the case.

(3) there is indeed an EMMA bug that has gone unnoticed all
these years.

You need to isolate the .class file that reproduces the
problem and attach it to this tracker issue. If you are
afraid of proprietary code disclosure in a single class,
email it to my SF alias.

I need this info to make further progress.

Vlad.

[Vlad Roubtsov]

Logged In: YES
user_id=1013207

Without more details, I am rejecting this as non-reproducible.

The issue is marked as pending, it will close in a couple of
weeks unless further info is added.

[sakshi]

Hi,

I am trying to instrument class files using emma with jdk 1.8 to get code coverage of my project.
using command- java -cp emma.jar emma instr -ip . -m overwrite -verbose

However, getting below error-

emma instr: unexpected failure:
Exception in thread "main" com.vladium.emma.EMMARuntimeException: unexpected failure:
at com.vladium.emma.Command.exit(Command.java:237)
at com.vladium.emma.instr.instrCommand.run(instrCommand.java:178)
at emma.main(emma.java:40)
Caused by: java.lang.IllegalStateException: CONSTANT_info: invalid tag value [18]
at com.vladium.jcd.cls.constant.CONSTANT_info.new_CONSTANT_info(CONSTANT_info.java:103)
at com.vladium.jcd.parser.ClassDefParser$classParser.constant_pool(ClassDefParser.java:168)
at com.vladium.jcd.parser.ClassDefParser$classParser.class_table(ClassDefParser.java:109)
at com.vladium.jcd.parser.ClassDefParser.parseClass(ClassDefParser.java:56)
at com.vladium.emma.instr.InstrProcessorST.handleFile(InstrProcessorST.java:468)
at com.vladium.util.IPathEnumerator$Factory$PathEnumerator.enumeratePathDir(IPathEnumerator.java:193)
at com.vladium.util.IPathEnumerator$Factory$PathEnumerator.enumerate(IPathEnumerator.java:97)
at com.vladium.emma.instr.InstrProcessorST._run(InstrProcessorST.java:715)
at com.vladium.emma.Processor.run(Processor.java:54)

I am using aspectj-maven-plugin in my project. However, even after removing this plugin, I am getting same error.
Does anyone know the reason of this error. Is there a way to troubleshoot this error?

Thanks in advance!
Sakshi

[dee]

Hi Sakshi,

Ran into same issue. How did you pass through this error.

Thanks in advance,
-Dee