-
Bug
-
Resolution: Fixed
-
P3
-
11.0.6, 13.0.2, 14, 15
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8245388 | 14u-cpu | Yasumasa Suenaga | P3 | Resolved | Fixed | master |
JDK-8245221 | 14.0.2 | Yasumasa Suenaga | P3 | Resolved | Fixed | b07 |
JDK-8257801 | 13.0.6 | Olga Mikhaltcova | P3 | Resolved | Fixed | b03 |
JDK-8276059 | 11.0.15-oracle | Harold Seigel | P3 | Resolved | Fixed | b01 |
JDK-8240823 | 11.0.8 | Yasumasa Suenaga | P3 | Resolved | Fixed | b01 |
```
PS > .\build\windows-x86_64-server-fastdebug\images\jdk日本語\bin\java.exe --version
Error occurred during initialization of VM
Failed setting boot class path.
```
I think this bug has been occurred since
It uses mbstowcs_s() to convert char* to wchar_t*. But Windows API for wchar_t* (they are named *W()) requires Unicode chars for their arguments. mbstowcs_s() would not convert to Unicode. We need to use MultiByteToWideChar().
This issue has been also confirmed in AdoptOpenJDK 11.0.6 [1]. So we also need to change jdk11u.
[1] https://github.com/AdoptOpenJDK/openjdk-build/issues/1496
- backported by
-
JDK-8240823 Cannot start JVM when $JAVA_HOME includes CJK characters
-
- Resolved
-
-
JDK-8245221 Cannot start JVM when $JAVA_HOME includes CJK characters
-
- Resolved
-
-
JDK-8245388 Cannot start JVM when $JAVA_HOME includes CJK characters
-
- Resolved
-
-
JDK-8257801 Cannot start JVM when $JAVA_HOME includes CJK characters
-
- Resolved
-
-
JDK-8276059 Cannot start JVM when $JAVA_HOME includes CJK characters
-
- Resolved
-
- duplicates
-
JDK-8275791 Cannot start JVM when path includes CJK characters
-
- Closed
-
- relates to
-
JDK-8242283 Can't start JVM when java home path includes non-ASCII character
-
- Closed
-
-
JDK-8240725 Some functions might not work with CJK character
-
- Closed
-
-
JDK-8191521 handle long relative path specified in -Xbootclasspath/a on windows
-
- Resolved
-
-
JDK-8241461 Can't start JVM when java path includes CJK chars and code-page is English
-
- Closed
-