Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8289284

jdk.tracePinnedThreads output confusing when pinned due to native frame

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • 20
    • 19, 20
    • core-libs
    • b06
    • Verified

    Description

      Running with -Djdk.tracePinnedThreads=full or -Djdk.tracePinnedThreads=short provides a stack trace when parking a virtual thread pins its carrier. If the reason for the pinning is a native frame, the output is currently:

      $CLASS.$METHOD(Native Method)) <== monitors:0

      The "<== monitors" suffix should not be printed for native frames.

      A secondary issue is that there is no stack trace when there is Panama downcall as there isn't a "native frame" to show in the output.

      Attachments

        Issue Links

          Activity

            People

              alanb Alan Bateman
              alanb Alan Bateman
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: