-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 7
-
Component/s: hotspot
-
b03
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2195072 | 7 | John Rose | P3 | Closed | Fixed | b99 |
| JDK-2197811 | 6u23 | John Rose | P3 | Resolved | Fixed | b01 |
| JDK-2199710 | 6u22m | John Rose | P3 | Resolved | Fixed | b01 |
| JDK-2197521 | 6u21p | John Rose | P3 | Resolved | Fixed | b03 |
The changes to constant pool accessors in 6939207 picked the wrong CP accessor for MethodComparator. The original change wrongly assumed the classes being compared had not yet been rewritten.
This causes an assertion "clean u2" to throw when using JVMTI class redefinition methods, in the debug build. It will also cause unpredictable failures on little-endian systems.
This causes an assertion "clean u2" to throw when using JVMTI class redefinition methods, in the debug build. It will also cause unpredictable failures on little-endian systems.
- backported by
-
JDK-2197521 MethodComparator uses the wrong CP index accessor
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-