RVM

JDWP & JVMTI support

Details

  • Type: New Feature New Feature
  • Status: In Progress In Progress
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 1000
  • Component/s: Runtime
  • Labels:
    None
  • Number of attachments :
    1

Description

Adding JDWP & JVMTI support
JDWP & JVMTI are standards introduced by sun to uniform the way JVM[s] are debugged/queried. They are not mandatory nor do they form requirements to comply with the JVM standard
Java Debug Wire Protocol is an interface specification to debug/query the JVM status. It defines the format of information and requests transferred between the process being debugged and the debugger front end. JVMTI s a low-level native interface ( based on JNI) that defines the services a Java virtual machine provides for tools such as debuggers and profilers(which they are implemented as agents).

Issue Links

Activity

Hide
Eslam AlMorshdy added a comment -

Collective patch for classpath-0.95 of the ongoing RVM-33
included
classpath-cvs.classpath30275
classpath-cvs.RVM-26
classpath-cvs.RVM-77

Show
Eslam AlMorshdy added a comment - Collective patch for classpath-0.95 of the ongoing RVM-33 included classpath-cvs.classpath30275 classpath-cvs.RVM-26 classpath-cvs.RVM-77
Hide
Eslam AlMorshdy added a comment -

helpful commands

-Running the rvm in server mode waiting for a consuming IDE
./rvm -Xms256m -Xmx1024m -X:processors=1 -X:runjdwp:transport=dt_socket,address=localhost:1234,server=y,suspend=n -X:use:rvm:socketimpl=y

Spying on the protocol
=================
In the eclipse 3.3RC4 installation run the following (older versions fail throwing exception)
java -cp plugins/org.eclipse.jdt.debug_3.3.0.v20070530a/jdimodel.jar:plugins/org.eclipse.osgi_3.3.0.v20070530.jar:plugins/com.ibm.icu_3.6.1.v20070417.jar org/eclipse/jdi/internal/spy/TcpipSpy 6900 localhost 1234

Testing with RvmSocket Implementation
===============================
add the following

  • X:use:rvm:socketimpl=y

IDE
===
You can attach a running rvm instance using eclipse->run->debg-
you may want to increase debugger time out in eclipse->preferences->java->OpenDebugDialog->Remotejava application

Running the debugger thread
=======================
kill -sigquit `ps aux | grep JikesRVM | tr -s [:blank:] | cut -d' ' -f 2 | tr "\n" ' '|cut -d ' ' -f1`

Show
Eslam AlMorshdy added a comment - helpful commands -Running the rvm in server mode waiting for a consuming IDE ./rvm -Xms256m -Xmx1024m -X:processors=1 -X:runjdwp:transport=dt_socket,address=localhost:1234,server=y,suspend=n -X:use:rvm:socketimpl=y Spying on the protocol ================= In the eclipse 3.3RC4 installation run the following (older versions fail throwing exception) java -cp plugins/org.eclipse.jdt.debug_3.3.0.v20070530a/jdimodel.jar:plugins/org.eclipse.osgi_3.3.0.v20070530.jar:plugins/com.ibm.icu_3.6.1.v20070417.jar org/eclipse/jdi/internal/spy/TcpipSpy 6900 localhost 1234 Testing with RvmSocket Implementation =============================== add the following
  • X:use:rvm:socketimpl=y
IDE === You can attach a running rvm instance using eclipse->run->debg- you may want to increase debugger time out in eclipse->preferences->java->OpenDebugDialog->Remotejava application Running the debugger thread ======================= kill -sigquit `ps aux | grep JikesRVM | tr -s [:blank:] | cut -d' ' -f 2 | tr "\n" ' '|cut -d ' ' -f1`

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:

Time Tracking

Estimated:
11w
Original Estimate - 11 weeks
Remaining:
11w
Remaining Estimate - 11 weeks
Logged:
Not Specified
Time Spent - Not Specified