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

SA: Incorrect BCI and Line Number with jstack if the top frame is in the interpreter

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 11
    • Fix Version/s: 12
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b24
    • CPU:
      x86
    • OS:
      generic

      Backports

        Description

        mail snippet from David Griffiths below
        =======================================================

        I have observed that if the top frame is in the interpreter it reports the BCI and line number incorrectly. This is because X86Frame.getInterpreterFrameBCI uses the value stored on the stack rather than the actual live value stored in R13.

        I have a patch for this which lets LinuxAMD64JavaThreadPDAccess.getCurrentFrameGuess pass the R13 value to X86Frame so that the latter can then do:

          public int getInterpreterFrameBCI() {
            Address bcp = addressOfInterpreterFrameBCX().getAddressAt(0);
            // If we are in the top level frame then R13 may have been set for us which contains
            // the BCP. If so then let it take priority. If we are in a top level interpreter frame,
            // the BCP is live in R13 (on x86) and not saved in the BCX stack slot.
            if (r13 != null) {
                bcp = r13;
            }
            Address methodHandle = addressOfInterpreterFrameMethod().getAddressAt(0);

        and this fixes the problem.

        ==============================================

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                jgeorge Jini George (Inactive)
                Reporter:
                jgeorge Jini George (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: