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

exception on init method not called but enter called causing nullpointer #5

Open
deanhiller opened this issue Jan 5, 2014 · 0 comments

Comments

@deanhiller
Copy link

I am not sure how to reproduce this and I worked around it by just doing if something != null but basically the bytecode stuff was wrapping enterMethod and exitMethod to be called around one of my methods(it seemed to always be the first method in my catch block) and initMethod was nevercalled.

Since initMethod was never called, I ended up with a nullpointer in enterMethod as it requires initMethod to be called.

The logic on whether to wire initMethod is strange in my opinion. The way it should be coded I would think is if(enterMethodAdded || exitMethodAdded) addInitMethod()

but instead it depends on different stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant