RFR: JDK-8264899: C1: -XX:AbortVMOnException does not work if all methods in the call stack are compiled with C1 and there are no exception handlers [v3]

[Damon Fenacci]

On Thu, 15 Jun 2023 10:13:29 GMT, Amit Kumar <amitkumar at openjdk.org> wrote:

>> @offamitkumar I noticed you have a few s390x commits. Could I ask you to run a few tests for s390? Thank you very much.
>
> Hi @dafedafe, On `Z15` machine, `TestAbortVmOnException.java` is failing with below error:
> 
> 
> ----------System.err:(36/2119)----------                                                                                                                    
>  stdout: [#                                                                                                                                                 
> # A fatal error has been detected by the Java Runtime Environment:                                                                                          
> #                                                                                                                                                           
> #  Internal Error (/home/amit/jdk/src/hotspot/share/oops/compressedOops.inline.hpp:138), pid=2449542, tid=2449543                                          
> #  assert(!is_null(v)) failed: narrow klass value can never be zero
> #
> # JRE version: OpenJDK Runtime Environment (22.0) (fastdebug build 22-internal-adhoc.amit.jdk)                                                             
> # Java VM: OpenJDK 64-Bit Server VM (fastdebug 22-internal-adhoc.amit.jdk, compiled mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, l$nux-s390x)
> # Problematic frame:
> # V  [libjvm.so+0x4bf1bc]  Runtime1::check_abort_on_vm_exception(oopDesc*)+0x83c                                                                           
> #
> # Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e" (or dumping to $home/amit/jdk/build/linux-s390x-server-fastdebug/test-support/jtreg_test_hotspot_jtreg_runtime_ErrorHandling_TestAbortVmOnException_java/scratch/0/core.244$542)
> #
> # An error report file with more information is saved as:
> # /home/amit/jdk/build/linux-s390x-server-fastdebug/test-support/jtreg_test_hotspot_jtreg_runtime_ErrorHandling_TestAbortVmOnException_java/scratch/0/hs_er$_pid2449542.log
> [1.053s][warning][os] Loading hsdis library failed
> #
> # If you would like to submit a bug report, please visit:
> #   https://bugreport.java.com/bugreport/crash.jsp
> #
> ];
>  stderr: []
>  exitValue = 134
> 
> java.lang.RuntimeException: 'fatal error: Saw MyAbortException, aborting' missing from stdout/stderr                                                       
>         at jdk.test.lib.process.OutputAnalyzer.shouldContain(OutputAnalyzer.java:221)                                                                ...

> > @offamitkumar I think I used the wrong register for the exception oop. It should be fixed now.
> 
> Thanks, for fixing it. Testing done for tier1-test with fastdebug, slowdebug on Z15 machine. No new failure appeared.

@offamitkumar thanks a lot for testing!

-------------

PR Comment: https://git.openjdk.org/jdk/pull/14240#issuecomment-1598241751