Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#1390] BytecodeParser update #442

Closed
wants to merge 2 commits into from

Conversation

Projects
None yet
4 participants
@sgodbillon
Copy link
Contributor

commented Jan 23, 2012

BytecodeParser update for bugfix.

@mbknor

This comment has been minimized.

Copy link
Member

commented Mar 12, 2012

Can you please clarify if this fix is for master/1.3 only?

@sgodbillon

This comment has been minimized.

Copy link
Contributor Author

commented Mar 12, 2012

Yes, this fix is only for master (BytecodeParser is not in use in 1.2.x).

@mbknor

This comment has been minimized.

Copy link
Member

commented Mar 12, 2012

thanks. merged into master

@mbknor mbknor closed this Mar 12, 2012

@deanhiller

This comment has been minimized.

Copy link

commented Dec 3, 2013

how do you debug these type of issues? How can I tell if it is javassist or bytecodeparser. I am trying to see if I can debug this. I am not sure if byte code is being manipulated before bytecodeparser or after(if after, the issue could be javassist, right). The specific call crash is in LVEnhancer when parser.analyze is called.

This is jdk 1.7 but that should work, right? (My other application is working fine with play 1.3.x).

java.lang.RuntimeException: WARN: popped a TOP!
at bytecodeparser.analysis.stack.Stack.pop(Stack.java:90) ~[bytecodeparser-0.3.jar:na]
at bytecodeparser.analysis.decoders.DecodedMethodInvocationOp.simulate(DecodedMethodInvocationOp.java:110) ~[bytecodeparser-0.3.jar:na]
at bytecodeparser.analysis.stack.StackAnalyzer.analyze(StackAnalyzer.java:126) [bytecodeparser-0.3.jar:na]

@xael-fry

This comment has been minimized.

Copy link
Member

commented Dec 4, 2013

Please do not comment in Closed issue, you can use the google group for question, or create a new issue in lighthouse if it is an issue
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.