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

CodeBlob::is_frame_complete_at() does not honor CodeOffsets::frame_never_safe

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P3
    • 9
    • 7u121, 8u112, 9
    • hotspot
    • b150

    Description

      Way back in JDK-6250767, CodeBlob::is_frame_complete_at() and CodeOffsets::frame_never_safe were introduced to support AsyncGetCallTrace. We still rely on this for pd_get_top_frame_for_profiling and friends. However, it appears this has been broken forever, and that even in the JDK-6250767 changeset, CodeBlob::is_frame_complete_at() would return true if the frame complete offset was CodeOffsets::frame_never_safe (-1), making the value effectively mean "always safe".

      Attachments

        Issue Links

          Activity

            People

              thartmann Tobias Hartmann
              dlong Dean Long
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: