RFR: 8289284: jdk.tracePinnedThreads output confusing when pinned due to native frame [v2]

[Jaikiran Pai]

On Wed, 13 Jul 2022 09:47:50 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
>
> Alan Bateman has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains three additional commits since the last revision:
> 
>  - PrintStream can auto flush
>  - Merge
>  - Initial commit

Thank you for the update. This looks fine to me.

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

Marked as reviewed by jpai (Reviewer).

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