Java Virtual Machine Tools Interface: Difference between revisions
Luckas-bot (talk | contribs) m r2.7.1) (Robot: Adding hu:Java Virtual Machine Tools Interface |
added category |
||
Line 3: | Line 3: | ||
The JVMTI is a native interface of the JVM. A library, written in [[C (programming language)|C]] or [[C++]], is loaded during the initialization of the JVM. The library has access to the JVM state by calling JVMTI and JNI ([[Java Native Interface]]) functions and can register to receive JVMTI events using event handler functions that are called by the JVM when such an event occurs. |
The JVMTI is a native interface of the JVM. A library, written in [[C (programming language)|C]] or [[C++]], is loaded during the initialization of the JVM. The library has access to the JVM state by calling JVMTI and JNI ([[Java Native Interface]]) functions and can register to receive JVMTI events using event handler functions that are called by the JVM when such an event occurs. |
||
JVMTI was defined through the [[Java Community Process]] by JSR-163 |
JVMTI was defined through the [[Java Community Process]] by JSR-163, the specification for the [[Java Platform Profiling Architecture]]. The JVMTI replaces the JVMPI (Java Virtual Machine Profiling Interface) and the JVMDI (Java Virtual Machine Debug Interface). The JVMPI and the JVMDI are declared as being deprecated in J2SE 5.0 and were removed in Java SE6. |
||
JVMTI is the lowest level of the [[Java Platform Debugger Architecture]]. |
JVMTI is the lowest level of the [[Java Platform Debugger Architecture]]. |
||
Line 12: | Line 12: | ||
*[http://java.sun.com/developer/technicalArticles/Programming/jvmpitransition/ The JVMPI Transition to JVMTI] |
*[http://java.sun.com/developer/technicalArticles/Programming/jvmpitransition/ The JVMPI Transition to JVMTI] |
||
⚫ | |||
[[Category:Java development tools]] |
[[Category:Java development tools]] |
||
[[Category:Java specification requests]] |
|||
⚫ | |||
[[hu:Java Virtual Machine Tools Interface]] |
[[hu:Java Virtual Machine Tools Interface]] |
Revision as of 16:30, 9 September 2012
Java Virtual Machine Tool Interface (JVMTI, or more properly, JVM TI) was introduced in J2SE 5.0 (Tiger). This interface allows a program to inspect the state and to control the execution of applications running in the Java Virtual Machine (JVM). JVMTI is designed to provide an Application Programming Interface (API) for the development of tools that need access to the state of the JVM. Examples for such tools are debuggers or profilers.
The JVMTI is a native interface of the JVM. A library, written in C or C++, is loaded during the initialization of the JVM. The library has access to the JVM state by calling JVMTI and JNI (Java Native Interface) functions and can register to receive JVMTI events using event handler functions that are called by the JVM when such an event occurs.
JVMTI was defined through the Java Community Process by JSR-163, the specification for the Java Platform Profiling Architecture. The JVMTI replaces the JVMPI (Java Virtual Machine Profiling Interface) and the JVMDI (Java Virtual Machine Debug Interface). The JVMPI and the JVMDI are declared as being deprecated in J2SE 5.0 and were removed in Java SE6.
JVMTI is the lowest level of the Java Platform Debugger Architecture.