The JVM Tool Interface (JVM TI): How VM Agents Work - The Diigo Meta page

• 31 Jan 12
  

  Elaine Wyq

  agent jvm java

  •  

     

    Because the agent library will be operating in the same process and address space as the VM itself, anything inside the agent code will run in the VM process too. A bad agent can crash the entire VM process with a trivial null pointer dereference. Agents can also be very difficult to get right. Agent libraries must be re-entrant and MT-safe, and they must follow all the JVM TI and JNI rules. For instance, if your agent leaks memory by calling malloc() and not doing the free(), then  the VM will appear to have a leak. Allocating too much memory will cause the VM process to fail with an out of memory  error. You must pay close attention to detail when you add an agent library.
• 29 Sep 11
  

  carlos puentes

  The JVM tool interface (JVM TI) is a standard native API that allows for native libraries to capture events and control a Java Virtual Machine (JVM) for the Java platform.* These native libraries are sometimes called agent libraries and are often used as a basis for the Java technology-level tool APIs, such as the Java Debugger Interface (JDI) that comes with the Java Development Kit (JDK). Profiler tool vendors will often need to create an agent library that uses JVM TI. This article explores some basics of writing a JVM TI agent library by walking through the heapTracker demo agent available in the JDK downloads.

  java.lang.instrument SE java how to

• 11 Dec 09
  

  kasperni

  jvm jvmti

• 05 Jun 09
  

  Sam Ye

  java_profiler

• 18 Jul 08
  

  Marcelo Castoldi

  barra favoritos Java

• 03 Mar 07
  

  Norman Kabir

  java profiler

• 17 Jan 07
  

  Emmanuel Hugonnet

  This article explores some basics of writing a JVM TI agent library by walking through the heapTracker demo agent available in the JDK downloads.

  jdk1.5 tools reference jvmti java

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.