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.

Sign up for GitHub

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

Jump to bottom

Unexpected behaviour on checkcast #105

Open
samczsun opened this issue Dec 29, 2016 · 1 comment
Open

Unexpected behaviour on checkcast #105

samczsun opened this issue Dec 29, 2016 · 1 comment

Comments

@samczsun
Copy link

It seems with the JVM, a checkcast on a null object instantly succeeds, and bypasses any class loading. This means that a simple

aconst_null
checkcast nonexistantclassname

will cause Krakatau to fail the decompilation of the method.

Even while running with -Xverify:all, the JVM does not seem to care about the nonexistent class.
@Storyyeller
Copy link
Owner

I looked into this, but unfortunately, I think it will take a fair bit of work to fix.

Storyyeller added a commit that referenced this issue Jan 2, 2017
@Storyyeller
Add test for checkcast of nonexistent class (#105)
53f539b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Storyyeller @samczsun