8366400: JCK test api/java_text/DecimalFormat/Parse.html fails after JDK-8363972 #27014
+14
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a JCK test failure of an unexpected SIOOBE during DecimalFormat parsing. During the char by char comparison in
matchAffix
, the minimum of the length of the parsed String and the PP index + affix length are iterated on. The parse position index needs to be checked to not be negative to ensure that we do not index the String below 0. Taking the minimum of those two previously mentioned values already guarantees that we do not index the String above the length.Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27014/head:pull/27014
$ git checkout pull/27014
Update a local copy of the PR:
$ git checkout pull/27014
$ git pull https://git.openjdk.org/jdk.git pull/27014/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27014
View PR using the GUI difftool:
$ git pr show -t 27014
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27014.diff
Using Webrev
Link to Webrev Comment