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

nsk.share.jdi.Debugee.isJFR_active() is incorrect and corresponsing logic seems to be broken

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 15
    • Fix Version/s: 15
    • Component/s: core-svc
    • Subcomponent:
    • Resolved In Build:
      b27

      Backports

        Description

        Some jdi tests use less strict checks when JFR is used. It is checked with

            public boolean isJFR_active() {
                String opts = argumentHandler.getLaunchOptions();
                int jfrPos = opts.indexOf("-XX:+FlightRecorder");

                if (jfrPos >= 0)
                    return true;
                else
                    return false;
            }

        However, the JFR is always enabled but not started by default. The line which used to run tests with JFR is
        "-XX:StartFlightRecording=dumponexit=true,maxsize=500M -XX:FlightRecorderOptions=repository=jfrrep"
        So tests unaware of JFR threads. Also, the JDI with Graal as JIT should be broken in the same way.

        It is needed to investigate how it really works.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  fmatte Fairoz Matte
                  Reporter:
                  lmesnik Leonid Mesnik
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: