RFR: 8346193: CrashGCForDumpingJavaThread do not trigger expected crash build with clang17 [v5]

[Kim Barrett]

On Thu, 2 Jan 2025 03:18:35 GMT, SendaoYan <syan at openjdk.org> wrote:

>> Sorry, got it now.
>> The duplicate `CrashGCForDumpingJavaThread` check has been removed.
>
> 1. --with-debug-level=optimized: `java -XX:+CrashGCForDumpingJavaThread -version` do not trigger jvm crash and print version meaasge.
> 2. --with-debug-level=release: `java -XX:+CrashGCForDumpingJavaThread -version` report VM option 'CrashGCForDumpingJavaThread' is develop and is available only in debug version of VM.
> 3. --with-debug-level=fastdebug: `java -XX:+CrashGCForDumpingJavaThread -version` trigger jvm crash correctly.

Good.  Those results are as expected.  In case it isn't clear, the reason for the difference between optimized
(no crash) and fastdebug (crash) is that optimized defaults VerifyBeforeExit to false, while for fastdebug it
defaults to true.  Enabling that option in an optimized build will crash in the same manner as fastdebug.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/22757#discussion_r1900547348