JDK-6823454 : Oop-typed loadP yields invalid pointer (0x1) on SPECjbb2005 at OSRed method entry
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-03-29
  • Updated: 2010-04-03
  • Resolved: 2009-04-08
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.
JDK 6 JDK 7 Other
6u18Fixed 7Fixed hs15Fixed
Description
See comments.

Comments
EVALUATION fetch_interpreter_state is treating T_ADDRESS as T_OBJECT when fetching the monitor state from the frame which leads to problems with verify oops. The fix is to treat T_ADDRESS as RawPtr.
01-04-2009

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/7230de7c4610
01-04-2009