JDK-6495056 : Badly formed debug statement in ReferenceProcessor::delete_null_referents_from_lists
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 1.4.2_13
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-11-17
  • Updated: 2015-04-13
  • Resolved: 2007-04-05
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.
Other
1.4.2_15 b01Fixed
Description
Using -XX options TraceReferenceGC and PrintGCDetails crashes 
hotspot.  We have lost part of a debug statement in 
ReferenceProcessor::delete_null_referents_from_lists which 
results in a null-pointer being followed. (a %s in a format
string with no follow-on argument provided)
Comments
SUGGESTED FIX In 1.4.2 we should probably print_cr a simple string for each of the 4 subsequent calls to delete_null_referents().
17-11-2006
EVALUATION 1.4.2_13 073 void ReferenceProcessor::delete_null_referents_from_lists() { 074 // loop over the lists 075 if (TraceReferenceGC && PrintGCDetails) { 076 gclog_or_tty->print_cr( 077 "\nScrubbing %s discovered list of Null referents"); // FAULT 078 } This line is from 5.0, but is not appropriate in 1.4.2.
17-11-2006