Why no hs-err file on CheckJNI?
thomas.stuefe at gmail.com
Mon Aug 23 14:27:10 UTC 2021
when we specify CheckJNI or CheckJNICalls and we catch an error (e.g. a
memory overwriter), we write a short report, then abort. See:
This has been introduced in 2008 with JDK-6739363 "Xcheck jni doesn't check
native function arguments". I could find no discussion about this on
mailing list archives.
Does anyone know why we don't write a normal hs-err file in this case?
Would anyone care if we did? We do so in similar cases, e.g. if os::free()
catches an overwrite.
More information about the hotspot-runtime-dev