JDK-8272703 : StressSeed should be set via FLAG_SET_ERGO
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 17,18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-08-19
  • Updated: 2021-10-05
  • Resolved: 2021-09-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 17 JDK 18
17.0.2Fixed 18 b17Fixed
Related Reports
Relates :  
Description
The StressSeed flag added by JDK-8252219 should be set via FLAG_SET_ERGO if the seed is generated by the VM (i.e., not set via the command line). This way, it will be added to the "[Global flags]" section of the hs_err file on crash and can be used to reproduce the issue.
Comments
Fix Request (17u) I would like to have it in 17u to improve compiler fuzzer reliability/reproducibility. Applies cleanly. Behaves the same way as mainline.
04-10-2021

> To trigger a crash, simply use -XX:CICrashAt=1 A bit of correction for testers: you need to reach C2 code, so it should be e.g. -XX:-TieredCompilation -Xcomp -XX:+StressLCM -XX:CICrashAt=1. Otherwise you just crash at very first C1 compilation, and no StressSeed would be hs_err :)
04-10-2021

Changeset: 66ce09f5 Author: Tobias Holenstein <tobias.holenstein@oracle.com> Committer: Tobias Hartmann <thartmann@openjdk.org> Date: 2021-09-23 12:55:42 +0000 URL: https://git.openjdk.java.net/jdk/commit/66ce09f51eb37029c8ba67a70f8c90a307dae1eb
23-09-2021

To trigger a crash, simply use -XX:CICrashAt=1
19-08-2021