JDK-5096280 : NEWHPROF: manual incorrectly specifies array object field
- Type: Bug
- Component: tools
- Sub-Component: hprof
- Affected Version: 5.0
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2004-09-02
- Updated: 2004-10-23
- Resolved: 2004-10-23
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| Other | JDK 6 |
|---|---|
| 5.0u10Resolved | 6 b10Fixed  |
Related Reports
|
Relates :
|
Description
This only relates to the binary format of hprof. > The first is a documentation error, I think. In the > "OBJECT ARRAY DUMP", it says the fourth element is the > "element class object ID." It's not; it's really the > array class object ID. That is, if there's an array > of Foo, this field points to the class "Foo[]", not to > the class "Foo". The element type is "Foo". It makes > more sense and is more useful to have an array class > object ID (that is, a pointer to the class "Foo[]", which > is what you get with JDK 1.5), so I think the thing to do > is change the docs. I don't know what JDK 1.2 did, or the > various intermediates.
Comments
|