JDK-6533620 : vtable stubs notification for JVMTI should happen after they are filled in
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8u60,9
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2007-03-12
  • Updated: 2023-07-21
  • Resolved: 2023-07-21
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 9
9Resolved
Related Reports
Duplicate :  
Description
The code which posts the creation of dynamic code for JVMTI currently posts the event for vtable stubs when a whole chunk is allocated but not filled in.  This means that tools which capture the code at creation time get the wrong contents.  It really should occur after they are filled in.

Comments
The problem was already fixed by JDK-8025841.
14-04-2015

SQE is ok to defer from 8u40.
01-12-2014

Moved label along with comment from backport Vladimir Ivanov added a comment - 2014-12-01 15:32 - edited Long standing issue (from the very beginning), which has minor impact on the users. Will be fixed in the next release (8u60).
01-12-2014

ILW=JVMTI get wrong vtable content, when tools capture content at creation time, none=MMH=P3
08-05-2014

EVALUATION The notification in vtableStubs.cpp should occur for each fill in.
12-03-2007