Integrated: 8289284: jdk.tracePinnedThreads output confusing when pinned due to native frame

Alan Bateman alanb at openjdk.org
Wed Jul 13 15:06:11 UTC 2022


On Tue, 28 Jun 2022 10:44:01 GMT, Alan Bateman <alanb at openjdk.org> wrote:

> The system property jdk.tracePinnedThreads triggers a stack trace to be printed when a virtual thread parks while pinned. If a virtual thread is pinned due to a native frame there is a spurious " <== monitors:0" added to line for the native method.
> 
> A secondary issue is that there is no stack trace when there is Panama downcall as there isn't a native method in the stack trace. A future change may annotate the downcalls, for now the entire stack trace is printed (no filtering) so there is at least some output when pinned due to a call through native code

This pull request has now been integrated.

Changeset: f528124f
Author:    Alan Bateman <alanb at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/f528124f571a29da49defbef30eeca04ab4a00ce
Stats:     115 lines in 4 files changed: 91 ins; 7 del; 17 mod

8289284: jdk.tracePinnedThreads output confusing when pinned due to native frame

Reviewed-by: jpai, mchung

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

PR: https://git.openjdk.org/jdk/pull/9308


More information about the core-libs-dev mailing list