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

fix a number of typos in the JVMTI spec

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 11
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b20

      Backports

        Description

        I forgot to push the typos that were in the RFR for JDK-8205113 from Jeremy.

        The missed update is:

        --- old/src/hotspot/share/prims/jvmti.xml 2018-06-15 09:26:41.322067153 -0700
        +++ new/src/hotspot/share/prims/jvmti.xml 2018-06-15 09:26:41.182067873 -0700
        @@ -778,7 +778,7 @@
         
           <intro id="bci" label="Bytecode Instrumentation">
             This interface does not include some events that one might expect in an interface with
        - profiling support. Some examples include object allocation events and full speed
        + profiling support. Some examples include full speed
             method enter and exit events. The interface instead provides support for
             <i>bytecode instrumentation</i>, the ability to alter the Java virtual machine
             bytecode instructions which comprise the target program. Typically, these alterations
        @@ -3454,7 +3454,7 @@
          <jint/>
          <description>
                     For <datalink id="JVMTI_HEAP_REFERENCE_FIELD"/>, the
        - referrer object is not a class or an inteface.
        + referrer object is not a class or an interface.
                     In this case, <code>index</code> is the index of the field
                     in the class of the referrer object.
                     This class is referred to below as <i>C</i>.
        @@ -8513,10 +8513,10 @@
          For the method indicated by <code>method</code>,
          return the beginning and ending addresses through
          <code>start_location_ptr</code> and <code>end_location_ptr</code>. In a
        - conventional byte code indexing scheme,
        + conventional bytecode indexing scheme,
          <code>start_location_ptr</code> will always point to zero
          and <code>end_location_ptr</code>
        - will always point to the byte code count minus one.
        + will always point to the bytecode count minus one.
               </description>
               <origin>jvmdi</origin>
               <capabilities>
        @@ -8649,8 +8649,8 @@
               <synopsis>Get Bytecodes</synopsis>
               <description>
          For the method indicated by <code>method</code>,
        - return the byte codes that implement the method. The number of
        - bytecodes is returned via <code>bytecode_count_ptr</code>. The byte codes
        + return the bytecodes that implement the method. The number of
        + bytecodes is returned via <code>bytecode_count_ptr</code>. The bytecodes
          themselves are returned via <code>bytecodes_ptr</code>.
               </description>
               <origin>jvmdi</origin>
        @@ -8673,13 +8673,13 @@
          <param id="bytecode_count_ptr">
          <outptr><jint/></outptr>
          <description>
        - On return, points to the length of the byte code array
        + On return, points to the length of the bytecode array
          </description>
          </param>
          <param id="bytecodes_ptr">
          <allocbuf outcount="bytecode_count_ptr"><uchar/></allocbuf>
          <description>
        - On return, points to the pointer to the byte code array
        + On return, points to the pointer to the bytecode array
          </description>
          </param>
               </parameters>
        @@ -8923,7 +8923,7 @@
                  layer of agents) this function allows each transformation
                  to have its own prefix.
                  The prefixes are applied in the order supplied and are
        - processed in the same manor as described for the
        + processed in the same manner as described for the
                  application of prefixes from multiple <jvmti/> environments
                  in <functionlink id="SetNativeMethodPrefix"/>.
                  <p/>
        @@ -12996,7 +12996,7 @@
               Agents that create more than one JVM TI environment, where the
               capability is added to some but not all environments, may observe the
               start phase beginning earlier in the JVM TI environments that possess
        - the capabilty.
        + the capability.
               <p/>
               In the case of VM start-up failure, this event will not be sent.
             </description>

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                jmanson Jeremy Manson
                Reporter:
                sspitsyn Serguei Spitsyn
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: