[
https://issues.apache.org/jira/browse/BCEL-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696185#comment-13696185
]
Sergey Mashkov edited comment on BCEL-168 at 6/29/13 7:47 PM:
--------------------------------------------------------------
It looks like we have to rebuild StackMapTable from scratch during method
generation.
I've tried BCEL code and it looks like it already have implementation we need
but I don't see ways to reuse it for now...
By the way I recommend to increase this issue priority to high or blocker.
was (Author: cy6ergn0m):
It looks like we have to rebuild StackMapTable from scratch during method
generation.
I've tried BCEL code and it looks like it already have implementation we need
but I don't see ways to reuse it for now...
> Stack map table problem with in JDK7 (java.lang.VerifyError: Expecting a
> stack map frame in method)
> ---------------------------------------------------------------------------------------------------
>
> Key: BCEL-168
> URL: https://issues.apache.org/jira/browse/BCEL-168
> Project: Commons BCEL
> Issue Type: Bug
> Components: Main
> Affects Versions: 5.2
> Environment: Operating System:
> Platform: PC
> Reporter: sam
> Assignee: Apache Commons Developers
>
> I want add local variable for a method. (using javaagent option)
> But when I try this with in JDK 7, I did face with java.lang.VerifyError
> (stack map offset problem)
> As I know, this problem is related with added new feature stack map table in
> JDK 7.
> So I've been search how to fix it, but almost of solution were change JDK
> version or use -XX option.
> But I don't want use it because I heard that if use SplitVerifier I will lose
> benefits of JDK7 default Verifier.
> Can I fix this problem use only BCEL or BCEL team have a plan to accommodate
> it?
--
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
