On Fri, 3 Dec 2021 07:29:17 GMT, Toshio Nakamura <tnakam...@openjdk.org> wrote:
> Could you review this fix? > > Problem: > Custom JRE generated by jlink cannot find non-ASCII named modules included > inside the JRE. > > Cause and fix: > If module or package name was composed by ASCII then non-ASCII characters, > ImageStringsReader:stringFromByteBufferMatches() miscalculated the length of > matched string. The first part of ASCII characters was missing. This patch > corrected the value. > > Testing: > tier1 and tier2 on Linux have no regression. > I wasn't able to create an automate test for this issue. I appreciate any > advice. This pull request has now been integrated. Changeset: fcd67a52 Author: Toshio Nakamura <tnakam...@openjdk.org> Committer: Naoto Sato <na...@openjdk.org> URL: https://git.openjdk.java.net/jdk/commit/fcd67a5242b7db06e4cb06b574972a463b209b2e Stats: 99 lines in 2 files changed: 98 ins; 0 del; 1 mod 8278185: Custom JRE cannot find non-ASCII named module inside Reviewed-by: naoto ------------- PR: https://git.openjdk.java.net/jdk/pull/6693
