-
Bug
-
Resolution: Fixed
-
P2
-
None
-
b40
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083926 | emb-9 | David Buck | P2 | Resolved | Fixed | team |
JDK-8065472 | 8u45 | David Buck | P2 | Resolved | Fixed | b01 |
JDK-8064324 | 8u40 | David Buck | P2 | Closed | Fixed | b15 |
JDK-8071107 | emb-8u47 | David Buck | P2 | Resolved | Fixed | team |
JDK-8072243 | 7u85 | David Buck | P2 | Resolved | Fixed | b01 |
JDK-8064327 | 7u80 | David Buck | P2 | Closed | Fixed | b04 |
JDK-8064347 | 6u91 | David Buck | P2 | Closed | Won't Fix | |
JDK-8064349 | 5.0u81 | David Buck | P2 | Closed | Won't Fix |
I did not notice this earlier as the porting work I did in jdk8003147 fixes generic support enough so that the corrupted classes pass HotSpot's bytecode verification. (Un)fortunately JRockit's byte code verification is much stricter and does not allow these classes to be loaded. This means that when JRockit uses BCEL to instrument classes, we end up unable to load the resulting classes. That means that this issue breaks JRockits byte code instrumentation for generic-using code.
- backported by
-
JDK-8065472 BCEL corrupts debug data of methods that use generics
-
- Resolved
-
-
JDK-8071107 BCEL corrupts debug data of methods that use generics
-
- Resolved
-
-
JDK-8072243 BCEL corrupts debug data of methods that use generics
-
- Resolved
-
-
JDK-8083926 BCEL corrupts debug data of methods that use generics
-
- Resolved
-
-
JDK-8064324 BCEL corrupts debug data of methods that use generics
-
- Closed
-
-
JDK-8064327 BCEL corrupts debug data of methods that use generics
-
- Closed
-
-
JDK-8064347 BCEL corrupts debug data of methods that use generics
-
- Closed
-
-
JDK-8064349 BCEL corrupts debug data of methods that use generics
-
- Closed
-
- relates to
-
JDK-8064516 BCEL still corrupts generic methods if bytecode offsets are modified
-
- Closed
-
-
JDK-8003147 port fix for BCEL bug 39695 to our copy bundled as part of jaxp
-
- Resolved
-