JDK-6280619 : jhat needs to tolerate incomplete/parial dumps
- Type: Enhancement
- Component: core-svc
- Sub-Component: tools
- Affected Version: 6
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-06-05
- Updated: 2010-08-24
- Resolved: 2005-09-17
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.
| JDK 6 |
|---|
6 b53Fixed  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
jmap allows to generate a HPROF heap dump from a core file or hung process. As this dump is taken from a snapshot of the process the dump may be incomplete - for example HPROF_GC_INSTANCE_DUMP records may have a class object ID that doesn't exist. Currently jhat can tolerate instance fields values that are object IDs of objects that are not in the heap. However if anything else is incomplete then the parser in jhat will throw an exception and abort. This RFE is submitted to update the jhat parser and model implementation so that it can tolerate incomplete dumps. This is important in most mortem scenarios where the dump is generated from a core file. ###@###.### 2005-06-05 12:39:53 GMT
Comments
|