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
AIOOBE in ProblemReporter.invalidType() #286
Comments
|
The code that throws: The values that I see when the AIOOBE is (about to be) thrown:
Maybe created here? I'm not 100% sure: So one is not a qualified type name, the other is. I assume that is where the bad index is coming from. Will have to check why one is qualified and the other is not... Weird that the object that doesn't have qualified The other (qualified) type is created here: (or a similar stack trace, still a problem binding due to "split packages") Actually I noticed the two types are different:
|
|
See this index check, added quite a while near the same code: cf7db1b#diff-fd23cf7032143d2ba23d68639ebe308a164cc8d86477e7e4598bca7291dfd71bR3322 |
This change adds index changes for ParameterizedQualifiedTypeReference and ArrayQualifiedTypeReference in ProblemReporter.invalidType(), similar to the existing index check for QualifiedTypeReference in the same method. Fixes: eclipse-jdt#286
|
Works fine on I20220804-0700 |
This change adds index changes for ParameterizedQualifiedTypeReference and ArrayQualifiedTypeReference in ProblemReporter.invalidType(), similar to the existing index check for QualifiedTypeReference in the same method. Fixes: eclipse-jdt#286
Most recent SDK build as of today (but can be reproduced on 4.21 too).
Right click
org.eclipse.jdt.internal.compiler.batch.ClasspathJar.filefield and say "Open Call Hierarchy"."Call Hierarchy" view will be empty but an error will be reported to the log.
Opening call hierarchy on other fields in same class seem to work fine.
The text was updated successfully, but these errors were encountered: