Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P3
Fix Version/s: hs17
Affects Version/s: 7
Component/s: hotspot
Labels:
- verify-waive-setup

Subcomponent:
runtime
Resolved In Build:
b06
CPU:

generic
OS:

generic

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2187059	7	Yumin Qi	P3	Closed	Fixed	b79
JDK-2187784	6-pool	Yumin Qi	P3	Closed	Won't Fix
JDK-2190011	6u21	Yumin Qi	P3	Closed	Fixed	b01
JDK-2187785	5.0u25	Yumin Qi	P3	Closed	Fixed	b02

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.

backported by

JDK-2187059 Print out stack trace for target thread of GC crash

Closed

JDK-2187784 Print out stack trace for target thread of GC crash

Closed

JDK-2187785 Print out stack trace for target thread of GC crash

Closed

JDK-2190011 Print out stack trace for target thread of GC crash

Closed

Assignee:: Yumin Qi

Reporter:: Coleen Phillimore

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2005-12-09 12:09

Updated:: 2012-10-13 08:18

Resolved:: 2010-01-14 07:52

Imported:: 17/Sep/12 7:06 AM

Indexed:: 19/Jul/12 10:21 PM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates