1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
/*
* Copyright 2000-2008 Sun Microsystems, Inc. All Rights Reserved.
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* This code is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License version 2 only, as
* published by the Free Software Foundation.
*
* This code is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
* version 2 for more details (a copy is included in the LICENSE file that
* accompanied this code).
*
* You should have received a copy of the GNU General Public License version
* 2 along with this work; if not, write to the Free Software Foundation,
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
*
* Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
* CA 95054 USA or visit www.sun.com if you need additional information or
* have any questions.
*
*/
package sun.jvm.hotspot.types;
import sun.jvm.hotspot.debugger.*;
/** <P> This is the basic interface which describes a field in a C/C++
data structure or a Java object. </P>
<P> The accessors in this class are designed to allow manual
coercion of the data within the field, which is often necessary
when interfacing with C programs. Therefore, the accessors here do
not perform any type checking. Specializations of the Field
interface, such as JByteField, provide getValue() methods which
both perform type checking and return the appropriate specialized
type. </P>
<P> See @see CIntegerType for a description of why all C integer
types are bundled into the category "CIntegerType". </P>
<P> As an example, coercing a pointer field into an int can be
done in the following fashion (assuming the application has
registered an integer type in the type database called
"intptr_t"): </P>
<PRE>
{
...
Address myObject = ...;
CIntegerType intptr_tType = (CIntegerType) db.lookupType("intptr_t");
long addrVal = field.getCInteger(myObject, intptr_tType);
...
}
</PRE>
FIXME: among other things, this interface is not sufficient to
describe fields which are themselves arrays (like symbolOop's
jbyte _body[1]). */
public interface Field {
/** Get the name of this field */
public String getName();
/** Get the type of this field */
public Type getType();
/** Get the size, in bytes, of this field. Used for manual data
structure traversal where necessary. */
public long getSize();
/** Is this a static field? */
public boolean isStatic();
/** The offset of this field, in bytes, in its containing data
structure, if nonstatic. If this is a static field, throws a
WrongTypeException. */
public long getOffset() throws WrongTypeException;
/** The address of this field, if it is a static field. If this is a
nonstatic field, throws a WrongTypeException. */
public Address getStaticFieldAddress() throws WrongTypeException;
/** <P> These accessors require that the field be nonstatic;
otherwise, a WrongTypeException will be thrown. Note that type
checking is not performed by these accessors in order to allow
manual type coercion of field data. For better protection when
accessing primitive fields, use the get(Type)Field accessors in
Type.java. </P>
<P> NOTE that the Address passed in to these routines may, in
fact, be an OopHandle. Specifically, in a reflective system,
dereferencing operations applied to the OopHandle must be
performed atomically with respect to GC. </P>
<P> See @see CIntegerType for a description of why all C integer
types are bundled into the category "CIntegerType". </P>
*/
public boolean getJBoolean (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public byte getJByte (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public char getJChar (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public short getJShort (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public int getJInt (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public long getJLong (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public float getJFloat (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public double getJDouble (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public long getCInteger (Address addr, CIntegerType type)
throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public Address getAddress (Address addr) throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public OopHandle getOopHandle(Address addr)
throws UnmappedAddressException, UnalignedAddressException, WrongTypeException, NotInHeapException;
public OopHandle getNarrowOopHandle(Address addr)
throws UnmappedAddressException, UnalignedAddressException, WrongTypeException, NotInHeapException;
/** <P> These accessors require that the field be static; otherwise,
a WrongTypeException will be thrown. Note that type checking is
not performed by these accessors in order to allow manual type
coercion of field data. For better protection when accessing
primitive fields, use the get(Type)Field accessors in
Type.java. </P>
<P> NOTE that the Address passed in to these routines may, in
fact, be an OopHandle. Specifically, in a reflective system,
dereferencing operations applied to the OopHandle must be
performed atomically with respect to GC. </P>
<P> See @see CIntegerType for a description of why all C integer
types are bundled into the category "CIntegerType". </P>
*/
public boolean getJBoolean () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public byte getJByte () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public char getJChar () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public float getJFloat () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public double getJDouble () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public int getJInt () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public long getJLong () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public short getJShort () throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public long getCInteger (CIntegerType type)
throws UnmappedAddressException, UnalignedAddressException, WrongTypeException;
public Address getAddress () throws UnmappedAddressException, UnalignedAddressException;
public OopHandle getOopHandle()
throws UnmappedAddressException, UnalignedAddressException, NotInHeapException;
public OopHandle getNarrowOopHandle()
throws UnmappedAddressException, UnalignedAddressException, NotInHeapException;
}
|
