It would be good if the error is properly propagated to the caller, and then we exit the VM with the usual exit sequence (or somehow continue, if the error happens inside jcmd dumping).
Note: much of the CDS dumping runs inside the VM thread, so we probably cannot use the usual TRAPS convention for error propagation. If we have to manually check for an error code at every function call, that may result in fragile code.
- relates to
-
JDK-8306476 CDS ArchiveHeapTestClass.java test asserts when vm_exit is called on VM thread
-
- Resolved
-
-
JDK-8334899 Test runtime/cds/appcds/javaldr/ExceptionDuringDumpAtObjectsInitPhase.java failed after JDK-8306580
-
- Resolved
-
-
JDK-8303422 Use common functions to exit the VM for -Xshare:dump and CDS errors
-
- Resolved
-
-
JDK-8306582 Remove MetaspaceShared::exit_after_static_dump()
-
- Resolved
-
-
JDK-8328623 ArchiveHeapTestClass.java failed with assert is_power_of_2(alignment)
-
- Closed
-
-
JDK-8334907 Test ExceptionDuringDumpAtObjectsInitPhase.java fail to initialize archive heap
-
- Closed
-
-
JDK-8306582 Remove MetaspaceShared::exit_after_static_dump()
-
- Resolved
-