JDK-8015265 : revise the fix for 8007037
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: hs25
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2013-05-23
  • Updated: 2017-01-11
  • Resolved: 2013-05-28
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 8 Other Other
8Fixed hs25Fixed hs25,openjdk7uFixed
Related Reports
Relates :  
Description
While working on a fix for 8014431, it was found that the fix for 8007037 in constantPool.cpp needs to be revised. Please refer to comment in 8007037 for details.
Comments
For convenience: This fix is broken: bool match = compare_entry_to(k1, cp2, k2, CHECK_false) && compare_operand_to(i1, cp2, i2, CHECK_false); You can not use CHECK_ macros on functions that are then subject to boolean comparison. The above will expand to: bool match = compare_entry_to(k1, cp2, k2, THREAD); if (HAS_PENDING_EXCEPTION) return false; (0) && compare_operand_to(i1, cp2, i2, THREAD); if (HAS_PENDING_EXCEPTION) return false; (0); So match has the wrong value. See discussion from: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2013-May/007332.html
23-05-2013

Moving to hotspot/jvmti to match the cat/subcat of 8007037.
23-05-2013