United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6461204 DebugNonSafepoints sometimes records out of range bcis
JDK-6461204 : DebugNonSafepoints sometimes records out of range bcis

Details
Type:
Bug
Submit Date:
2006-08-17
Status:
Resolved
Updated Date:
2010-04-02
Project Name:
JDK
Resolved Date:
2006-11-14
Component:
hotspot
OS:
solaris_9
Sub-Component:
compiler
CPU:
sparc
Priority:
P4
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
hs10 (b03)

Related Reports
Backport:
Backport:
Relates:

Sub Tasks

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.

                                    

Comments
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.
                                     
2006-08-17
SUGGESTED FIX

http://analemma.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/c2_baseline/2006/20060818173730.never.sux/workspace/webrevs/webrev-2006.08.18/index.html
                                     
2006-08-21



Hardware and Software, Engineered to Work Together