DebugNonSafepoints sometimes records out of range bcis

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • hs10
    • Affects Version/s: 7
    • Component/s: hotspot
    • None
    • 6
    • b03
    • sparc
    • solaris_9

        Sometimes when running with PrintNMethods assertions are thrown because the bci recorded for a PcDesc isn't larger than the code size of the corresponding method. This only occurs with -XX:+DebugNonSafepoints because bcis are being pulled from instructions that didn't have the right bci on them. These are usually synthetics branches where GraphBuilder wasn't being careful about what scope the goto was actually in and the bci wasn't being used for other purposes so weren't detecting it was wrong before.

              Assignee:
              Tom Rodriguez
              Reporter:
              Tom Rodriguez
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: