-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 5.0, 6
-
Component/s: hotspot
-
b69
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2133514 | 5.0u8 | Daniel Daugherty | P4 | Resolved | Fixed | b01 |
During the code review process for 6338927, Jim Holmlund
noticed that previously EMCP methods are not marked as
obsolete. During a JVM/TI RedefineClasses() call, all
old methods are considered either obsolete or EMCP. At
that time, obsolete methods are marked as such. A subsequent
RedefineClasses() call can make a method that was previously
EMCP to be obsolete. In that case, we do not mark the EMCP
method as obsolete. I believe this oversight is a day one
bug in the RedefineClasses code.
noticed that previously EMCP methods are not marked as
obsolete. During a JVM/TI RedefineClasses() call, all
old methods are considered either obsolete or EMCP. At
that time, obsolete methods are marked as such. A subsequent
RedefineClasses() call can make a method that was previously
EMCP to be obsolete. In that case, we do not mark the EMCP
method as obsolete. I believe this oversight is a day one
bug in the RedefineClasses code.
- backported by
-
JDK-2133514 previously EMCP methods not marked as obsolete
-
- Resolved
-
- relates to
-
-
- Resolved
-