On Tue, 4 Oct 2022 12:50:22 GMT, Julian Waters <jwat...@openjdk.org> wrote:
>> Please review a small patch for dumping the failure reason when the MSVCRT >> libraries or the Java Virtual Machine fails to load on Windows, which can >> provide invaluable insight when debugging related launcher issues. >> >> See https://bugs.openjdk.org/browse/JDK-8292016 and the related Pull Request >> for the reason that the existing JLI error reporting utility was not used in >> this enhancement > > Julian Waters has updated the pull request incrementally with one additional > commit since the last revision: > > Make DLL_ERROR4 look a little better without changing what it means Results from usage in JDK-8288293 Failure to load the JVM (before): `Error: loading: D:\Eclipse\Workspace\HotSpot\jdk\build\windows-x86_64-server-release\jdk\bin\server\jvm.dll` Failure to load the JVM (after): `Error: Could not load D:\Eclipse\Workspace\HotSpot\jdk\build\windows-x86_64-server-release\jdk\bin\server\jvm.dll: The specified module could not be found` ------------- PR: https://git.openjdk.org/jdk/pull/9749
