-
Bug
-
Resolution: Fixed
-
P3
-
5.0
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2137101 | 5.0u10 | Kelly Ohair | P4 | Closed | Cannot Reproduce |
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.
> 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.
- backported by
-
JDK-2137101 NEWHPROF: manual incorrectly specifies array object field
-
- Closed
-
- relates to
-
JDK-6315235 SA: jmap heap dumper does not use correct class ID for object arrays
-
- Resolved
-