JDK-8293611 : Add a test for SIGQUIT handling under -XX:+ReduceSignalUsage
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 20
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2022-09-09
  • Updated: 2024-01-16
  • Resolved: 2024-01-16
Related Reports
Blocks :  
JDK-8234262 - Unmask SIGQUIT in a child process
Description
During review for JDK-8292695, we tried to add a test that checks that under -XX:+ReduceSignalUsage, SIGQUIT should make the process terminate abnormally.

However, this is difficult due to JDK-8234262. Even the workaround of passing -XX:+ReduceSignalUsage to the parent process did not work, probably due to how jtreg launches the parent process with "@run main/othervm -XX:+ReduceSignalUsage". Another possible workaround is to write a shell test instead of using a Java process (ProcessBuilder API) to launch the subprocess. I uploaded the non-working version here: https://github.com/caoman/jdk/commit/73e3a5f90985fcad9a383c704429cefb07011932

It is better to wait for JDK-8234262 to be fixed, then add this test.
Comments
Runtime Triage: This is not on our current list of priorities. We will consider this feature if we receive additional customer requirements.
16-01-2024