提交 c5871620 编写于 作者: K kamg

7033669: JVM TI spec has to be changed to not contain URLS to the VM Spec

Summary: Update JVMTI source files to remove hyperlinks and add full legal name
Reviewed-by: acorn, dcubed, dholmes
上级 f9cf0ae7
...@@ -280,10 +280,8 @@ ...@@ -280,10 +280,8 @@
<!ELEMENT externallink (#PCDATA|jvmti|code|i|b|tm)*> <!ELEMENT externallink (#PCDATA|jvmti|code|i|b|tm)*>
<!ATTLIST externallink id CDATA #REQUIRED> <!ATTLIST externallink id CDATA #REQUIRED>
<!ELEMENT vmspeclink EMPTY> <!ELEMENT vmspec EMPTY>
<!ATTLIST vmspeclink id CDATA #IMPLIED> <!ATTLIST vmspec chapter CDATA #IMPLIED>
<!ATTLIST vmspeclink name CDATA #IMPLIED>
<!ATTLIST vmspeclink preposition CDATA #IMPLIED>
<!ELEMENT internallink (#PCDATA|jvmti|code|i|b)*> <!ELEMENT internallink (#PCDATA|jvmti|code|i|b)*>
<!ATTLIST internallink id CDATA #REQUIRED> <!ATTLIST internallink id CDATA #REQUIRED>
...@@ -2285,9 +2283,8 @@ jvmtiEnv *jvmti; ...@@ -2285,9 +2283,8 @@ jvmtiEnv *jvmti;
Stack frames are referenced by depth. Stack frames are referenced by depth.
The frame at depth zero is the current frame. The frame at depth zero is the current frame.
<p/> <p/>
Stack frames are as described in the Stack frames are as described in
<vmspeclink id="Overview.doc.html#17257" <vmspec chapter="3.6"/>,
name="Frames section"/>.
That is, they correspond to method That is, they correspond to method
invocations (including native methods) but do not correspond to platform native or invocations (including native methods) but do not correspond to platform native or
VM internal frames. VM internal frames.
...@@ -2627,7 +2624,7 @@ err = (*jvmti)-&gt;Deallocate(jvmti, stack_info); ...@@ -2627,7 +2624,7 @@ err = (*jvmti)-&gt;Deallocate(jvmti, stack_info);
<param id="use_java_stack"> <param id="use_java_stack">
<jboolean/> <jboolean/>
<description> <description>
Return the stack showing the <vmspeclink/> Return the stack showing <vmspec/>
model of the stack; model of the stack;
otherwise, show the internal representation of the stack with otherwise, show the internal representation of the stack with
inlined and optimized methods missing. If the virtual machine inlined and optimized methods missing. If the virtual machine
...@@ -2707,7 +2704,7 @@ err = (*jvmti)-&gt;Deallocate(jvmti, stack_info); ...@@ -2707,7 +2704,7 @@ err = (*jvmti)-&gt;Deallocate(jvmti, stack_info);
When the thread is resumed, the execution When the thread is resumed, the execution
state of the thread is reset to the state state of the thread is reset to the state
immediately before the called method was invoked. immediately before the called method was invoked.
That is (using the <vmspeclink/> terminology): That is (using <vmspec/> terminology):
<ul> <ul>
<li>the current frame is discarded as the previous frame becomes the current one</li> <li>the current frame is discarded as the previous frame becomes the current one</li>
<li>the operand stack is restored--the argument values are added back <li>the operand stack is restored--the argument values are added back
...@@ -2868,9 +2865,8 @@ err = (*jvmti)-&gt;Deallocate(jvmti, stack_info); ...@@ -2868,9 +2865,8 @@ err = (*jvmti)-&gt;Deallocate(jvmti, stack_info);
to return at any point during its execution. to return at any point during its execution.
The method which will return early is referred to as the <i>called method</i>. The method which will return early is referred to as the <i>called method</i>.
The called method is the current method The called method is the current method
(as defined by the (as defined by
<vmspeclink id="Overview.doc.html#17257" <vmspec chapter="3.6"/>)
name="Frames section"/>)
for the specified thread at for the specified thread at
the time the function is called. the time the function is called.
<p/> <p/>
...@@ -3576,10 +3572,8 @@ class C2 extends C1 implements I2 { ...@@ -3576,10 +3572,8 @@ class C2 extends C1 implements I2 {
<field id="index"> <field id="index">
<jint/> <jint/>
<description> <description>
The index into the constant pool of the class. See the The index into the constant pool of the class. See the description in
<vmspeclink id="ClassFile.doc.html#20080" <vmspec chapter="4.4"/>.
name="Constant Pool section"/>
description.
</description> </description>
</field> </field>
</typedef> </typedef>
...@@ -5006,9 +5000,8 @@ class C2 extends C1 implements I2 { ...@@ -5006,9 +5000,8 @@ class C2 extends C1 implements I2 {
For references of this kind the <code>referrer_index</code> For references of this kind the <code>referrer_index</code>
parameter to the <internallink id="jvmtiObjectReferenceCallback"> parameter to the <internallink id="jvmtiObjectReferenceCallback">
jvmtiObjectReferenceCallback</internallink> is the index into jvmtiObjectReferenceCallback</internallink> is the index into
constant pool table of the class, starting at 1. See the constant pool table of the class, starting at 1. See
<vmspeclink id="ClassFile.doc.html#20080" <vmspec chapter="4.4"/>.
name="Constant Pool section"/>
</constant> </constant>
</constants> </constants>
...@@ -6441,9 +6434,7 @@ class C2 extends C1 implements I2 { ...@@ -6441,9 +6434,7 @@ class C2 extends C1 implements I2 {
been recorded as an initiating loader. Each been recorded as an initiating loader. Each
class in the returned array was created by this class loader, class in the returned array was created by this class loader,
either by defining it directly or by delegation to another class loader. either by defining it directly or by delegation to another class loader.
See the See <vmspec chapter="5.3"/>.
<vmspeclink id="ConstantPool.doc.html#72007"
name="Creation and Loading section"/>.
<p/> <p/>
For JDK version 1.1 implementations that don't For JDK version 1.1 implementations that don't
recognize the distinction between initiating and defining class loaders, recognize the distinction between initiating and defining class loaders,
...@@ -6626,9 +6617,7 @@ class C2 extends C1 implements I2 { ...@@ -6626,9 +6617,7 @@ class C2 extends C1 implements I2 {
For the class indicated by <code>klass</code>, return the access For the class indicated by <code>klass</code>, return the access
flags flags
via <code>modifiers_ptr</code>. via <code>modifiers_ptr</code>.
Access flags are defined in the Access flags are defined in <vmspec chapter="4"/>.
<vmspeclink id="ClassFile.doc.html"
name="Class File Format chapter"/>.
<p/> <p/>
If the class is an array class, then its public, private, and protected If the class is an array class, then its public, private, and protected
modifiers are the same as those of its component type. For arrays of modifiers are the same as those of its component type. For arrays of
...@@ -6794,9 +6783,8 @@ class C2 extends C1 implements I2 { ...@@ -6794,9 +6783,8 @@ class C2 extends C1 implements I2 {
<description> <description>
For the class indicated by <code>klass</code>, For the class indicated by <code>klass</code>,
return the minor and major version numbers, return the minor and major version numbers,
as defined in the as defined in
<vmspeclink id="ClassFile.doc.html" <vmspec chapter="4"/>.
name="Class File Format chapter"/>.
</description> </description>
<origin>new</origin> <origin>new</origin>
<capabilities> <capabilities>
...@@ -6839,10 +6827,8 @@ class C2 extends C1 implements I2 { ...@@ -6839,10 +6827,8 @@ class C2 extends C1 implements I2 {
<description> <description>
For the class indicated by <code>klass</code>, For the class indicated by <code>klass</code>,
return the raw bytes of the constant pool in the format of the return the raw bytes of the constant pool in the format of the
<code>constant_pool</code> item of the <code>constant_pool</code> item of
<vmspeclink id="ClassFile.doc.html" <vmspec chapter="4"/>.
name="Class File Format"
preposition="in"/>.
The format of the constant pool may differ between versions The format of the constant pool may differ between versions
of the Class File Format, so, the of the Class File Format, so, the
<functionlink id="GetClassVersionNumbers">minor and major <functionlink id="GetClassVersionNumbers">minor and major
...@@ -7286,9 +7272,7 @@ class C2 extends C1 implements I2 { ...@@ -7286,9 +7272,7 @@ class C2 extends C1 implements I2 {
<field id="class_bytes"> <field id="class_bytes">
<inbuf incount="class_byte_count"><uchar/></inbuf> <inbuf incount="class_byte_count"><uchar/></inbuf>
<description> <description>
Bytes defining class (in the Bytes defining class (in <vmspec chapter="4"/>)
<vmspeclink id="ClassFile.doc.html"
name="Class File Format"/>)
</description> </description>
</field> </field>
</typedef> </typedef>
...@@ -7611,10 +7595,8 @@ class C2 extends C1 implements I2 { ...@@ -7611,10 +7595,8 @@ class C2 extends C1 implements I2 {
<paramlink id="signature_ptr"/>. <paramlink id="signature_ptr"/>.
<p/> <p/>
Field signatures are defined in the JNI Specification and Field signatures are defined in the JNI Specification and
are referred to as are referred to as <code>field descriptors</code> in
<vmspeclink id="ClassFile.doc.html#14152" <vmspec chapter="4.3.2"/>.
name="field descriptors"
preposition="in"/>.
</description> </description>
<origin>jvmdiClone</origin> <origin>jvmdiClone</origin>
<capabilities> <capabilities>
...@@ -7709,9 +7691,7 @@ class C2 extends C1 implements I2 { ...@@ -7709,9 +7691,7 @@ class C2 extends C1 implements I2 {
<description> <description>
For the field indicated by <code>klass</code> and <code>field</code> For the field indicated by <code>klass</code> and <code>field</code>
return the access flags via <code>modifiers_ptr</code>. return the access flags via <code>modifiers_ptr</code>.
Access flags are defined in the Access flags are defined in <vmspec chapter="4"/>.
<vmspeclink id="ClassFile.doc.html"
name="Class File Format chapter"/>.
</description> </description>
<origin>jvmdi</origin> <origin>jvmdi</origin>
<capabilities> <capabilities>
...@@ -7810,10 +7790,9 @@ class C2 extends C1 implements I2 { ...@@ -7810,10 +7790,9 @@ class C2 extends C1 implements I2 {
return the method name via <code>name_ptr</code> and method signature via return the method name via <code>name_ptr</code> and method signature via
<code>signature_ptr</code>. <code>signature_ptr</code>.
<p/> <p/>
Method signatures are defined in the JNI Specification and are referred to as Method signatures are defined in the JNI Specification and are
<vmspeclink id="ClassFile.doc.html#7035" referred to as <code>method descriptors</code> in
name="method descriptors" <vmspec chapter="4.3.3"/>.
preposition="in"/>.
Note this is different Note this is different
than method signatures as defined in the <i>Java Language Specification</i>. than method signatures as defined in the <i>Java Language Specification</i>.
</description> </description>
...@@ -7902,9 +7881,7 @@ class C2 extends C1 implements I2 { ...@@ -7902,9 +7881,7 @@ class C2 extends C1 implements I2 {
<description> <description>
For the method indicated by <code>method</code>, For the method indicated by <code>method</code>,
return the access flags via <code>modifiers_ptr</code>. return the access flags via <code>modifiers_ptr</code>.
Access flags are defined in the Access flags are defined in <vmspec chapter="4"/>.
<vmspeclink id="ClassFile.doc.html"
name="Class File Format chapter"/>.
</description> </description>
<origin>jvmdi</origin> <origin>jvmdi</origin>
<capabilities> <capabilities>
...@@ -7941,9 +7918,7 @@ class C2 extends C1 implements I2 { ...@@ -7941,9 +7918,7 @@ class C2 extends C1 implements I2 {
including the local variables used to pass parameters to the including the local variables used to pass parameters to the
method on its invocation. method on its invocation.
<p/> <p/>
See <code>max_locals</code> in the See <code>max_locals</code> in <vmspec chapter="4.7.3"/>.
<vmspeclink id="ClassFile.doc.html#1546"
name="Code Attribute section"/>.
</description> </description>
<origin>jvmdi</origin> <origin>jvmdi</origin>
<capabilities> <capabilities>
...@@ -8150,8 +8125,7 @@ class C2 extends C1 implements I2 { ...@@ -8150,8 +8125,7 @@ class C2 extends C1 implements I2 {
The local variable's type signature, encoded as a The local variable's type signature, encoded as a
<internallink id="mUTF">modified UTF-8</internallink> string. <internallink id="mUTF">modified UTF-8</internallink> string.
The signature format is the same as that defined in The signature format is the same as that defined in
<vmspeclink id="ClassFile.doc.html#14152" <vmspec chapter="4.3.2"/>.
name="Field Descriptors section"/>
</description> </description>
</field> </field>
<field id="generic_signature"> <field id="generic_signature">
...@@ -10460,10 +10434,7 @@ myInit() { ...@@ -10460,10 +10434,7 @@ myInit() {
<synopsis>Add To Bootstrap Class Loader Search</synopsis> <synopsis>Add To Bootstrap Class Loader Search</synopsis>
<description> <description>
This function can be used to cause instrumentation classes to be defined by the This function can be used to cause instrumentation classes to be defined by the
bootstrap class loader. See bootstrap class loader. See <vmspec chapter="5.3.1"/>.
<vmspeclink id="ConstantPool.doc.html#79383"
name="Loading Using the Bootstrap Class Loader"
preposition="in"/>.
After the bootstrap After the bootstrap
class loader unsuccessfully searches for a class, the specified platform-dependent class loader unsuccessfully searches for a class, the specified platform-dependent
search path <paramlink id="segment"/> will be searched as well. Only one segment may be specified in search path <paramlink id="segment"/> will be searched as well. Only one segment may be specified in
...@@ -10480,7 +10451,7 @@ myInit() { ...@@ -10480,7 +10451,7 @@ myInit() {
contain any classes or resources other than those to be defined by the bootstrap contain any classes or resources other than those to be defined by the bootstrap
class loader for the purposes of instrumentation. class loader for the purposes of instrumentation.
<p/> <p/>
The <vmspeclink/> specifies that a subsequent attempt to resolve a symbolic <vmspec/> specifies that a subsequent attempt to resolve a symbolic
reference that the Java virtual machine has previously unsuccessfully attempted reference that the Java virtual machine has previously unsuccessfully attempted
to resolve always fails with the same error that was thrown as a result of the to resolve always fails with the same error that was thrown as a result of the
initial resolution attempt. Consequently, if the JAR file contains an entry initial resolution attempt. Consequently, if the JAR file contains an entry
...@@ -10512,10 +10483,7 @@ myInit() { ...@@ -10512,10 +10483,7 @@ myInit() {
<synopsis>Add To System Class Loader Search</synopsis> <synopsis>Add To System Class Loader Search</synopsis>
<description> <description>
This function can be used to cause instrumentation classes to be This function can be used to cause instrumentation classes to be
defined by the system class loader. See defined by the system class loader. See <vmspec chapter="5.3.2"/>.
<vmspeclink id="ConstantPool.doc.html#79441"
name="Loading Using a User-defined Class Loader"
preposition="in"/>.
After the class loader unsuccessfully searches for a class, the specified platform-dependent search After the class loader unsuccessfully searches for a class, the specified platform-dependent search
path <paramlink id="segment"/> will be searched as well. Only one segment may be specified in the path <paramlink id="segment"/> will be searched as well. Only one segment may be specified in the
<paramlink id="segment"/>. This function may be called multiple times to add multiple segments, the <paramlink id="segment"/>. This function may be called multiple times to add multiple segments, the
...@@ -10536,7 +10504,7 @@ myInit() { ...@@ -10536,7 +10504,7 @@ myInit() {
which takes a single parameter of type <code>java.lang.String</code>. The method is not required which takes a single parameter of type <code>java.lang.String</code>. The method is not required
to have <code>public</code> access. to have <code>public</code> access.
<p/> <p/>
The <vmspeclink/> specifies that a subsequent attempt to resolve a symbolic <vmspec/> specifies that a subsequent attempt to resolve a symbolic
reference that the Java virtual machine has previously unsuccessfully attempted reference that the Java virtual machine has previously unsuccessfully attempted
to resolve always fails with the same error that was thrown as a result of the to resolve always fails with the same error that was thrown as a result of the
initial resolution attempt. Consequently, if the JAR file contains an entry initial resolution attempt. Consequently, if the JAR file contains an entry
...@@ -11438,7 +11406,7 @@ myInit() { ...@@ -11438,7 +11406,7 @@ myInit() {
at the finest granularity allowed by the VM. A single step event is at the finest granularity allowed by the VM. A single step event is
generated whenever a thread reaches a new location. generated whenever a thread reaches a new location.
Typically, single step events represent the completion of one VM Typically, single step events represent the completion of one VM
instruction as defined in the <vmspeclink/>. However, some implementations instruction as defined in <vmspec/>. However, some implementations
may define locations differently. In any case the may define locations differently. In any case the
<code>method</code> and <code>location</code> <code>method</code> and <code>location</code>
parameters uniquely identify the current location and allow parameters uniquely identify the current location and allow
...@@ -13841,7 +13809,7 @@ typedef void (JNICALL *jvmtiEventVMInit) ...@@ -13841,7 +13809,7 @@ typedef void (JNICALL *jvmtiEventVMInit)
and can_get_source_debug_extension. and can_get_source_debug_extension.
PopFrame cannot have a native calling method. PopFrame cannot have a native calling method.
Removed incorrect statement in GetClassloaderClasses Removed incorrect statement in GetClassloaderClasses
(see http://java.sun.com/docs/books/vmspec/2nd-edition/html/ConstantPool.doc.html#79383). (see <vmspec chapter="4.4"/>).
</change> </change>
<change date="24 July 2003" version="v79"> <change date="24 July 2003" version="v79">
XML and text fixes. XML and text fixes.
......
...@@ -1039,34 +1039,14 @@ typedef struct { ...@@ -1039,34 +1039,14 @@ typedef struct {
</a> </a>
</xsl:template> </xsl:template>
<xsl:template match="vmspeclink"> <xsl:template match="vmspec">
<xsl:if test="count(@id)=1"> <cite>
<a> <xsl:text>The Java&#8482; Virtual Machine Specification</xsl:text>
<xsl:attribute name="href"> <xsl:if test="count(@chapter)=1">
<xsl:text>http://java.sun.com/docs/books/vmspec/2nd-edition/html/</xsl:text> <xsl:text>, Chapter </xsl:text>
<xsl:value-of select="@id"/> <xsl:value-of select="@chapter"/>
</xsl:attribute> </xsl:if>
<xsl:value-of select="@name"/> </cite>
</a>
<xsl:text> </xsl:text>
<xsl:choose>
<xsl:when test="count(@preposition)=1">
<xsl:value-of select="@preposition"/>
</xsl:when>
<xsl:otherwise>
<xsl:text>of</xsl:text>
</xsl:otherwise>
</xsl:choose>
<xsl:text> the </xsl:text>
</xsl:if>
<a>
<xsl:attribute name="href">
<xsl:text>http://java.sun.com/docs/books/vmspec/</xsl:text>
</xsl:attribute>
<i>
<xsl:text>Java Virtual Machine Specification</xsl:text>
</i>
</a>
</xsl:template> </xsl:template>
<xsl:template match="internallink"> <xsl:template match="internallink">
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册