RFR: JDK-8321017: Record in JFR that IEEE rounding mode was corrupted by loading a library [v2]
Thomas Stuefe
stuefe at openjdk.org
Wed Dec 6 08:09:32 UTC 2023
On Wed, 6 Dec 2023 07:31:20 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:
> > The cases where we directly dlopen/dlsym/fcn-call in the JDK codebase are probably not covered by the JNI checker, right ?
>
> Right. JNI checking is for checking actual JNI API functions, so I don't see where this would go. A call from Java code into a native method (from which native code could trigger the problem) is not a JNI call.
It is a flag to enable checks on third-party JNI code, so in my mind it fits perfectly. It also enables periodic signal handler checks. So, what's preventing us to fatal out when we detect this kind of problem and if -Xcheck:jni is set? It would be possible to do this in a delayed fashion.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/16903#issuecomment-1842368279
More information about the hotspot-dev
mailing list