RFR: 8291917: Windows - Improve error messages when the C Runtime Libraries or jvm.dll cannot be loaded [v11]

[Julian Waters]

On Wed, 5 Oct 2022 11:00:16 GMT, Julian Waters <jwaters at 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 with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains 13 additional commits since the last revision:
> 
>  - Merge branch 'openjdk:master' into patch-4
>  - Make DLL_ERROR4 look a little better without changing what it means
>  - Revert changes to JLI_ReportErrorMessageSys
>  - Update java_md.c
>  - Update java_md.h
>  - Merge branch 'openjdk:master' into patch-4
>  - Merge branch 'openjdk:master' into patch-4
>  - Back out change to DLL_ERROR4 for separate RFE
>  - Missing spacing between errors
>  - Introduce warning when system error cannot be determined
>  - ... and 3 more: https://git.openjdk.org/jdk/compare/e9cb88a8...e7bef513

Minor change:
From
`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`
to
`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