[JBoss JIRA] (JASSIST-160) Java.lang.VerifyErrors occur in specific cases when using javaassist with Java 1.7
8:31 p.m.
Avner Singerman created JASSIST-160:
---------------------------------------
Summary: Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
We found at least two different cases where inserting bytecode using javaassist results in
a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Avner Singerman updated JASSIST-160:
------------------------------------
Attachment: jatest.zip
Test case for this bug.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:32 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Falko M. commented on JASSIST-160:
----------------------------------
This seems to cause problems for many powermock-users (including me), see:
http://code.google.com/p/powermock/issues/detail?id=355#c42
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:43 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Tyler Brown commented on JASSIST-160:
-------------------------------------
From the PowerMock issue thread. Anyone trying to temporarily
workaround this issue, adding the following argument -XX:-UseSplitVerifier does prevent
this from occurring.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba resolved JASSIST-160.
-----------------------------------
Fix Version/s: 3.17.0-GA
Resolution: Done
To fix various errors related to stackmap tables, I have rewritten the whole
javassist.bytecode.stackmap package. Now Javassist generates a write stack map table as
far as I tested.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:15 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Desmond Kirrane commented on JASSIST-160:
-----------------------------------------
Does done not seem to fix the PowerMock issue:
http://code.google.com/p/powermock/issues/detail?id=355
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:15 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Desmond Kirrane edited comment on JASSIST-160 at 9/19/12 12:14 PM:
-------------------------------------------------------------------
Does not seem to fix the PowerMock issue:
http://code.google.com/p/powermock/issues/detail?id=355
was (Author: muppet_tizer):
Does done not seem to fix the PowerMock issue:
http://code.google.com/p/powermock/issues/detail?id=355
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba reopened JASSIST-160:
-----------------------------------
Really? I will check this.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:48 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
I have committed a revised version, which should have fixed the PowerMock issue.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Desmond Kirrane commented on JASSIST-160:
-----------------------------------------
Yes PowerMock issue is fixed now. Thanks for the quick turnaround.
Any release date for javassist-3.17.0-GA?
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba resolved JASSIST-160.
-----------------------------------
Resolution: Done
3.17.0-GA will be released in a week.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Thomas H commented on JASSIST-160:
----------------------------------
Hi. I think the issue still exists if powermock is used for testing classes extending the
SwingWorker. See the powermock issue and the modified example:
[http://code.google.com/p/powermock/issues/detail?id=355#c61]. Maybe if the problem occurs
in javassist, you can fix this for the next version.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
OK, I will check this.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
Yes, it was a bug. So I have fixed.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Thomas H commented on JASSIST-160:
----------------------------------
I have verified the bugfix to the powermock sample and it works fine. Now the new version
could be released and add to the maven repository, so that the powermock project can
modify the dependency to this version and release a new version themself. Thanks for the
quick bugfix.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Oliver Hernandez commented on JASSIST-160:
------------------------------------------
I'd like to add another error message that seems to be the result of this same bug:
{{java.lang.VerifyError: Bad type on operand stack in aaload in method
org.foo.bar.FooBar.<init>()V at offset 101}}
My use case is also with PowerMock, and the unit test involves mocking construction of a
new object using PowerMockito.whenNew(). Researching this problem led me here, and
applying the latest javassist-3.17.0-GA.jar resolved this error in my test.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:51 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
John Bainbridge commented on JASSIST-160:
-----------------------------------------
I just pull trunk and i noticed that this fixed most of the promblems however not all.
Here are my stack traces:
Exception in thread "main" java.lang.IllegalStateException: Failed to transform
class with name xxx.xxxxx.xxxxx.xxxxxx. Reason: null
at
org.powermock.core.classloader.MockClassLoader.loadMockClass(MockClassLoader.java:207)
at
org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:145)
at
org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:67)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:114)
at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:125)
at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49)
at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:390)
at sun.reflect.annotation.AnnotationParser.parseClassValue(AnnotationParser.java:371)
at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673)
at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480)
at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306)
at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241)
at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88)
at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70)
at java.lang.Class.initAnnotationsIfNecessary(Class.java:3089)
at java.lang.Class.getAnnotations(Class.java:3069)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.classAnnotations(PowerMockJUnit44RunnerDelegateImpl.java:165)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.getDescription(PowerMockJUnit44RunnerDelegateImpl.java:157)
at
org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.getDescription(JUnit4TestSuiteChunkerImpl.java:172)
at
org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.getDescription(AbstractCommonPowerMockRunner.java:47)
at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:40)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:520)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1060)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:884)
Caused by: java.lang.NullPointerException
at javassist.bytecode.stackmap.TypeData.commonSuperClassEx(TypeData.java:400)
at javassist.bytecode.stackmap.TypeData$TypeVar.fixTypes2(TypeData.java:342)
at javassist.bytecode.stackmap.TypeData$TypeVar.fixTypes(TypeData.java:325)
at javassist.bytecode.stackmap.TypeData$TypeVar.dfs(TypeData.java:270)
at javassist.bytecode.stackmap.MapMaker.fixTypes(MapMaker.java:287)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:140)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:99)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:423)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:405)
at javassist.expr.ExprEditor.doit(ExprEditor.java:113)
at javassist.CtClassType.instrument(CtClassType.java:1398)
at
org.powermock.core.transformers.impl.MainMockTransformer.transform(MainMockTransformer.java:75)
at
org.powermock.core.classloader.MockClassLoader.loadMockClass(MockClassLoader.java:203)
... 27 more
and :
java.lang.VerifyError: Stack map does not match the one at exception handler 2290 in
method xxx.xxxxx.xxx.xxxxxxx.xxxxxxxx()Ljava/lang/String; at offset 686
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2442)
at java.lang.Class.getMethod0(Class.java:2685)
at java.lang.Class.getMethod(Class.java:1620)
at org.easymock.internal.ObjectMethodsFilter.<init>(ObjectMethodsFilter.java:55)
at org.easymock.internal.MocksControl.createMock(MocksControl.java:59)
at org.powermock.api.easymock.PowerMock.doCreateMock(PowerMock.java:2212)
at org.powermock.api.easymock.PowerMock.doMock(PowerMock.java:2163)
at org.powermock.api.easymock.PowerMock.createMock(PowerMock.java:89)
at xxx.xxxx.xxx.xxxx.xxxxxxxxxxxxxxTest.testxxxxxxxxxx(xxxxxxxxxxxxxxTest.java:93)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:312)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.executeTest(PowerMockJUnit44RunnerDelegateImpl.java:296)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTestInSuper(PowerMockJUnit47RunnerDelegateImpl.java:112)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit47RunnerDelegateImpl$PowerMockJUnit47MethodRunner.executeTest(PowerMockJUnit47RunnerDelegateImpl.java:73)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$PowerMockJUnit44MethodRunner.runBeforesThenTestThenAfters(PowerMockJUnit44RunnerDelegateImpl.java:284)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:209)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:148)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:122)
at
org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:120)
at
org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:102)
at
org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:53)
at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:42)
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba reopened JASSIST-160:
-----------------------------------
any concrete test case?
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:01 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
John Bainbridge commented on JASSIST-160:
-----------------------------------------
When I'm trying to mock final class as well as a Serializable implenatation. I'll
try to come up with some dummy test cases for you.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:03 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
thanks.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Jacob m commented on JASSIST-160:
---------------------------------
Any chance that Johns issue could be opened as a new bug? I would really love to see a
public release of 3.17.0-GA as it fixes a lot of problems for people using PowerMock with
Java 1.7.
This issue would remain open as long as any verify errors turns up, no matter the nature
of it. I suggest one issue for each verify error type to make it easier to get stuff
released... :)
Thank you for fixing the issues - great work!
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Lisa Henderson commented on JASSIST-160:
----------------------------------------
I agree with Jacom M - it would be extremely valuable to release 3.17.0-GA to publish the
issue solution to date. Is there a release date being considered?
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:48 a.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
OK, I will check other issues and release GA as soon as possible.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba resolved JASSIST-160.
-----------------------------------
Resolution: Done
The bug reported by John Bainbridge has not been fixed yet.
John, if you make a test case, can you file it as a separate issue?
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:31 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
John Bainbridge commented on JASSIST-160:
-----------------------------------------
Yeah. I'm working on trying to come up with valid test case.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:15 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba updated JASSIST-160:
----------------------------------
Comment: was deleted
(was: A stackmap-related bug in Hibernate has been discussed at Javassist-163.)
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
ami tabak commented on JASSIST-160:
-----------------------------------
Hon. Professor Chiba
Can you estimate when the 3.17 GA will be released.
Sincerely
Ami Tabak
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:24 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
Although I'm still waiting for final checks, I hope it will be released within this
week.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:16 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
I have released 3.17.0-GA. It will be available from:
www.javassist.org
It will be also available from maven and sonotype.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Jacob m commented on JASSIST-160:
---------------------------------
This is great news! Thank you.
Do you know when it will be available through maven?
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Shigeru Chiba commented on JASSIST-160:
---------------------------------------
It will be today or on Monday.
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:57 p.m.
[
https://issues.jboss.org/browse/JASSIST-160?page=com.atlassian.jira.plugi...
]
Roger Glover commented on JASSIST-160:
--------------------------------------
Hmmm. Not up yet on Monday, unless I'm looking in the wrong places:
* http://mvnrepository.com/artifact/org.javassist/javassist
* http://mirrors.ibiblio.org/maven2/org/javassist/javassist/
*
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.javassist%22%20AND...
Java.lang.VerifyErrors occur in specific cases when using javaassist
with Java 1.7
----------------------------------------------------------------------------------
Key: JASSIST-160
URL: https://issues.jboss.org/browse/JASSIST-160
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: jdk1.7.0_03 on Windows XP SP 3
Reporter: Avner Singerman
Assignee: Shigeru Chiba
Fix For: 3.17.0-GA
Attachments: jatest.zip
We found at least two different cases where inserting bytecode using javaassist results
in a class that cannot be loaded with Java 1.7.
java.lang.VerifyError: Inconsistent stackmap frames at branch target
java.lang.VerifyError: Bad return type in method
The exact same code injection on the exact same classes works fine with Java 1.6.
We upgraded to the latest version of javaassist - 3.16.1.GA, but it didn't solve the
problem.
I'm attaching to this bug a self contained example where you can see both type of
errors.
More details in "Steps to Reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4183
days inactive
4426
days old
31 comments
12 participants
participants (12)
-
ami tabak (JIRA) -
Avner Singerman (JIRA)
-
Desmond Kirrane (JIRA)
-
Falko M. (JIRA)
-
Jacob m (JIRA)
-
John Bainbridge (JIRA)
-
Lisa Henderson (JIRA)
-
Oliver Hernandez (JIRA)
-
Roger Glover (JIRA)
-
Shigeru Chiba (JIRA)
-
Thomas H (JIRA)
-
Tyler Brown (JIRA)