JDWP: Remove JVM_OnLoad from library, only use AgentOnLoad in JVMTI backend

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 5.0
    • Affects Version/s: 5.0
    • Component/s: core-svc
    • tiger
    • generic
    • generic


      This is just a reminder bug

      Only do this after many builds past B19.

      -kto

      ###@###.### 2003-09-22

      Before B19, the Agent-OnLoad external would only be used if the
      -agentlib syntax at startup was used. With B19 of hotspot, if an -Xrun
      library didn't have a JVM_OnLoad, but did have an Agent_OnLoad external,
      then the -Xrun of this library would behave as a -agentlib and the
      Agent_OnLoad interface would be called.

      Prior to this change in the Backend, it had both OnLoad() interfaces.
      After this change it will only have the Agent_OnLoad interface
      (plus Agent_OnUnload).

      This means that ALL JDI, jdwp, jdb, etc. testing that uses -Xrun syntax
      will silently be getting the -agentlib semantics. This isn't expected to
      be a problem, but I feel compelled to point it out.

      So far no testing issues have come up with this, and it is expected to
      be stable.

            Assignee:
            Kelly Ohair (Inactive)
            Reporter:
            Kelly Ohair (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: