RFR: 8295974: jni_FatalError and Xcheck:jni warnings should print the native stack when there are no Java frames [v4]
Robbin Ehn
rehn at openjdk.org
Mon Jan 2 08:01:52 UTC 2023
On Fri, 23 Dec 2022 01:18:34 GMT, David Holmes <dholmes at openjdk.org> wrote:
>> If a JNI Fatal error, or a JNI warning (from Xcheck:jni) is triggered in "top-level" native code (such as the launcher itself, or a freshly attached native thread) then there is no stack printed as there are no Java frames. This enhancement changes that so that we print the native stack, similarly to how error reporting does. We reuse VMError::print_native _stack to do this, but it could be argued this should be moved to a more general purpose utility class - suggestions welcome.
>>
>> Testing:
>> - manual fault injection (see bug report)
>> - tiers 1-4
>>
>> Thanks.
>
> David Holmes has updated the pull request incrementally with one additional commit since the last revision:
>
> Move assertion and make clear print_jni_stack is only for current thread.
Marked as reviewed by rehn (Reviewer).
-------------
PR: https://git.openjdk.org/jdk/pull/11703
More information about the hotspot-dev
mailing list