United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6361589 Print out stack trace for target thread of GC crash
JDK-6361589 : Print out stack trace for target thread of GC crash

Details
Type:
Enhancement
Submit Date:
2005-12-09
Status:
Closed
Updated Date:
2012-10-13
Project Name:
JDK
Resolved Date:
2010-01-14
Component:
hotspot
OS:
generic
Sub-Component:
runtime
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
hs17 (b06)

Related Reports
Backport:
Backport:
Backport:
Backport:

Sub Tasks

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
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/547f81740344
                                     
2009-12-12
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/547f81740344
                                     
2009-12-23



Hardware and Software, Engineered to Work Together