|
Quick Lists
|
|
Bug ID:
|
6461204
|
|
Votes
|
0
|
|
Synopsis
|
DebugNonSafepoints sometimes records out of range bcis
|
|
Category
|
hotspot:compiler1
|
|
Reported Against
|
|
|
Release Fixed
|
hs10(b03),
6u4(b03) (Bug ID:2171815)
, 7(b03) (Bug ID:2176750)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
6712105
|
|
Submit Date
|
17-AUG-2006
|
|
Description
|
Sometimes when running with PrintNMethods assertions are thrown because the bci recorded for a PcDesc isn't larger than the code size of the corresponding method. This only occurs with -XX:+DebugNonSafepoints because bcis are being pulled from instructions that didn't have the right bci on them. These are usually synthetics branches where GraphBuilder wasn't being careful about what scope the goto was actually in and the bci wasn't being used for other purposes so weren't detecting it was wrong before.
Posted Date : 2006-08-17 16:59:17.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The fix is to add an assert in the code which emits the debug info so that these are detected early instead of only when printing.
Posted Date : 2006-08-17 17:00:18.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
