8263632: Improve exception handling of APIs in classLoader.cpp #3203
Please review this change which includes:
Testing: tiers 1,2 (passed); tiers 3,4 (in progress).
To checkout this PR locally:
To update a local copy of the PR:
@calvinccheung This change now passes all automated pre-integration checks.
After integration, the commit message for the final commit will be:
At the time when this comment was updated there had been 35 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
@calvinccheung Since your change was applied there have been 38 commits pushed to the
Your commit was automatically rebased without conflicts.
Pushed as commit c9d2d02.
On 3/28/21 9:40 PM, David Holmes wrote:
During VM bootstrap, classLoader.cpp tries to open files on related to
For --patch-module handling, throw_exception=false was specified.
For bootclasspath handling, throw_exception=true was specified before
But this will not throw any exception for invalid JAR files:
??  the file doesn't exist.
??  the file exists but is not a ZIP file
The behavior of  is due to this: is_init_completed() is false during
?? // Don't complain about bad jar files added via -Xbootclasspath/a:.
create_class_path_entry() is called when is_init_completed() is true
On 30/03/2021 9:01 am, Ioi Lam wrote:
Thanks for the explanations Ioi!