The Attach to VM dialog box enables you to connect the Java debugger to
an application running on another virtual machine. You open this
dialog box by choosing Debug Attach from the main window.
When you attach the Java debugger to a virtual machine, you will see threads as if you were debugging locally. If you have source code for the debugged application and you set a breakpoint in the code, the Source Editor will open with the breakpoint line highlighted.
The first item in the Attach to VM dialog box is the Debugger Type combo box. The IDE supports the JPDA and JDK 1.1 debugger implementations. The JDK 1.1 debugger implementation is available only if you are running J2SE software, version 1.3 or earlier.
The remainder of the items in the Attach to VM dialog box depend on the debugger implementation and transport implementation you are using. Full documentation of the shared memory and socket transports is available at http://java.sun.com/j2se/1.3/docs/guide/jpda/conninv.html.
The JPDA reference implementation provides a socket transport on both Solaris environments and Microsoft Windows systems. The Attach to VM dialog box prompts you for the following information:
The JPDA reference implementation provides a shared memory transport on the Microsoft Windows system only. The Attach to VM dialog box prompts you for the following information:
![]() |
If you are working on a Microsoft Windows system and the shared memory connector is not available, try
including the following startup parameter your
IDE-home/bin/ide.cfg file:
-J-Dnetbeans.debugger.jpda.transport=dt_shmem This parameter forces the IDE to use the shared memory connection when starting a debugging session with the Debug![]() |
The Attach to VM dialog box prompts you for the following information:
See also | |
---|---|
Attaching the Debugger to a Running Process |