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

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 9
    • Affects Version/s: 7u121, 8u112, 9
    • Component/s: hotspot
    • b150

      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".

            Assignee:
            Tobias Hartmann
            Reporter:
            Dean Long
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: