-
Enhancement
-
Resolution: Fixed
-
P5
-
6
-
b13
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2176905 | 7 | Daniel Daugherty | P3 | Closed | Fixed | b13 |
JDK-2171771 | 6u4 | Daniel Daugherty | P3 | Resolved | Fixed | b03 |
as a replacement for JVMPI. The members of the Expert Group felt that one
major release cycle (that is 1.6) was sufficent to convert tools based on JVMPI.
JVMTI is basically an enhanced JVMDI, so JVMDI is no longer needed. To our
knowledge the only products based on JVMDI are Sun's -- the JPDA back-end (which
has already been converted to JVMTI) and jdbx. JVMDI has also been used in
some university research projects.
Maintaining JVMPI and JVMDI in the VM is a significant maintenance burden,
as the VM changes there interfaces break. Their presence complicates the
VM code. And finally, even when off, JVMPI has a performance impact.
- backported by
-
JDK-2171771 Remove JVMPI in Dolphin/JDK7/Java7
- Resolved
-
JDK-2176905 Remove JVMPI in Dolphin/JDK7/Java7
- Closed
- duplicates
-
JDK-6513560 Remove suggestion to mail jvmpi_eol from fatal error message
- Closed
- relates to
-
JDK-6387310 include/jvmpi.h is missed
- Closed
-
JDK-6913186 a number of vm tests failed against jdk 5.0 with HS 16 nightly build
- Closed
-
JDK-6533127 fix for 4914266 reveals CHECK_UNHANDLED_OOPS compilation problems
- Closed
-
JDK-6265756 Remove JVMDI
- Resolved
-
JDK-4639363 Java Platform Profiling Architecture (JSR-163)
- Resolved