Why no hs-err file on CheckJNI?

[Thomas Stüfe]

Hi,

when we specify CheckJNI or CheckJNICalls and we catch an error (e.g. a
memory overwriter), we write a short report, then abort. See:

https://github.com/openjdk/jdk/blob/594e5161b48382d61509b4969bc8f52c3c076452/src/hotspot/share/prims/jniCheck.hpp#L36-L41

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.

Thanks, Thomas