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

Potential NPE in DefaultJavaType.getFullyQualifiedName() #111

Open
kwin opened this issue Sep 13, 2022 · 0 comments
Open

Potential NPE in DefaultJavaType.getFullyQualifiedName() #111

kwin opened this issue Sep 13, 2022 · 0 comments

Comments

@kwin
Copy link
Contributor

kwin commented Sep 13, 2022

There is a potential NPE in DefaultJavaType.getFullyQualifiedName (

StringBuilder result = new StringBuilder( resolveRealClass().getFullyQualifiedName() );
) when being called on an unresolvable type. This is particularly nasty as getFullyQualifiedName() may be called by equals(...).

That affects even more methods on DefaultJavaType (namely all those which unconditionally dereference the return value from resolveRealClass which may return null).

As it may happen that an instance of DefaultJavaType is not resolvable this should be treated more gracefully.

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