-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8273039: JShell crashes when naming variable or method "abstract" or "strictfp" #5897
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
Conversation
|
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
| } | ||
|
|
||
| @Override | ||
| public void visitModifiers(JCModifiers tree) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question can't we report this error when the erroneous code is being parsed? adding this method to Attr makes me feel a bit uncomfortable, I can understand if this is the only / best way though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parser will report the error, and will wrap the (presumed) modifiers into an erroneous tree, so the AST is reasonable. But JShell runs javac with --should-stop=at=FLOW, so the error in parser will not stop the processing, and when Attr will look into the erroneous tree, it will fail.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks for the clarification
vicente-romero-oracle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
@lahodaj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 425 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
/integrate |
|
Going to push as commit 2f20b0d.
Your commit was automatically rebased without conflicts. |
When JShell processes
int strictfp = 0;(which is obviously erroneous), it will speculativelly try to parse and attribute code along these lines:This crashes
Attr, as thestrictfpwill be wrapped inJCModifiers, wrapped inside an erroneous tree, andAttrdoes not handle modifiers.The proposal is to let
Attr"handle" theJCModifiersin an error-recovery situation.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5897/head:pull/5897$ git checkout pull/5897Update a local copy of the PR:
$ git checkout pull/5897$ git pull https://git.openjdk.java.net/jdk pull/5897/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5897View PR using the GUI difftool:
$ git pr show -t 5897Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5897.diff