JDK-6361589 : Print out stack trace for target thread of GC crash
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-12-09
- Updated: 2012-10-13
- Resolved: 2010-01-14
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 | JDK 7 | Other |
|---|---|---|---|
| 5.0u25,hs17Fixed | 6u21Fixed  |
7Fixed |
hs17Fixed |
Description
The hs_err* file prints out the thread stack for a thread that crashes, but in the case of a GC thread, the thread that it was gc'ing is more useful for diagnosing what is wrong. Maybe also in the process we can point to the frame that was doing gc and it's oopmaps and anything else we can salvage from the process. The hs_err*log information has been backported to 1.4.2 and when implemented, this should be too.
Comments
|