JDK-7120448 : Fix FP values for compiled frames in frame::describe
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs23
  • Priority: P5
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-12-12
  • Updated: 2012-04-10
  • Resolved: 2012-04-10
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 7 JDK 8 Other
7u4Fixed 8Fixed hs23Fixed
Related Reports
Relates :  
JDK-7141259 - Native stack is missing in hs_err
Description
For a compiled frame, the frame top depends on the initial (unextended) sp and the compiled frame size.

frame::describe has not been completely fixed. Its uses of [extended] sp() and of [non computed] fp() can result in a bad top address being printed and being used as a boundary while dumping compiled frames
Comments
EVALUATION http://hg.openjdk.java.net/lambda/lambda/hotspot/rev/eaa9557116a2
22-03-2012
EVALUATION http://hg.openjdk.java.net/hsx/hotspot-comp/hotspot/rev/eaa9557116a2
19-01-2012
EVALUATION frame::describe() was calling the platform dependent frame::fp() to get the frame pointer. Unfortunately, the semantic of frame::fp() is not clearly defined. On compiled x86 frames, the value could be arbitrary. That could cause frame::describe to dump misleading information and useless memory slots. Defined a new frame::real_fp() with a more precise semantic for portable shared code. This is the value expected by the platform ABI when it defines a frame pointer register. It may differ from the effective value of the FP register when that register is used in the JVM for other purposes (like compiled frames on some platforms). On other platforms, it is defined so that the stack area used by this frame goes from real_fp() to sp(). By default, the new definition is equivalent to the old frame::fp() definition. x86 is the only OpenJDK supported platform which required a different definition.
16-01-2012