Jump to: navigation, search

Difference between revisions of "Support seamless debugging between JDT and CDT"

Line 37: Line 37:
  
 
* code is available on svn
 
* code is available on svn
** svn co https://eclipse-incub.svn.sourceforge.net/svnroot/eclipse-incub/jni_seamless_debugging jni_seamless_debugging
+
** svn co https://eclipse-incub.svn.sourceforge.net/svnroot/eclipse-incub/org.eclipse.soc.jni org.eclipse.soc.jni
  
 
===Third step : tests and debugging===
 
===Third step : tests and debugging===
Line 47: Line 47:
  
 
==Roadmap==
 
==Roadmap==
* until end of gsoc - 31 August 2007:
 
** continue to write JUnit tests
 
** creation of screencasts
 
 
* 0.0.3 - 15 September 2007 (planned)
 
** All written tests must succeed
 
  
 
* 0.0.4 - 15 October 2007 (planned)
 
* 0.0.4 - 15 October 2007 (planned)
 
** jvm started in native code debugging
 
** jvm started in native code debugging
 +
** see ho integrate in eclipse CDT ?
  
 
==Documentation==
 
==Documentation==
Line 64: Line 59:
 
Simply add this site as "new remote site" :
 
Simply add this site as "new remote site" :
  
http://eclipse-incub.svn.sourceforge.net/viewvc/*checkout*/eclipse-incub/jni_seamless_debugging/update-site/site.xml
+
http://eclipse-incub.svn.sourceforge.net/viewvc/*checkout*/eclipse-incub/org.eclipse.soc.jni/update-site/site.xml
  
The sources are included in the Jar, but you can get them with subversion with the following command :  
+
The sources are included in the Jar, but you can get them on the subversion repository:  
  
svn co https://eclipse-incub.svn.sourceforge.net/svnroot/eclipse-incub/jni_seamless_debugging
+
https://eclipse-incub.svn.sourceforge.net/svnroot/eclipse-incub/org.eclipse.soc.jni
 +
 
 +
( You may have to install the subclipe plug-in )
  
 
===How to use the plug-in ?===
 
===How to use the plug-in ?===
Line 86: Line 83:
 
====Third step====
 
====Third step====
 
Set the correct settings for each tab.
 
Set the correct settings for each tab.
 
* JNI tab
 
*:Nothing for the moment
 
  
 
*C/C++ project tab  
 
*C/C++ project tab  
Line 104: Line 98:
  
 
====Fourth step====
 
====Fourth step====
The debug perspective will be launched, with the 2 debuggers. Ready to debug !
+
The debug perspective will be launched with the 2 debuggers. Ready to debug !
 
[[Image:Soc_jni_Debug_perspective.png|frame|center]]
 
[[Image:Soc_jni_Debug_perspective.png|frame|center]]
  
 
===How to report a bug/ask for an enhancement ?===  
 
===How to report a bug/ask for an enhancement ?===  
  
On the eclipse bugzilla there is a "org.eclipse.soc.jni" component for the "SOC" product in the "Technology" category. Please include the version of the plug-in and the max infos you can obtain.
+
On the eclipse bugzilla there is a "org.eclipse.soc.jni" component for the "SOC" product in the "Technology" category. Please include the version of the plug-in and the maximum infos you can obtain.
  
 
==FAQ==
 
==FAQ==
Line 115: Line 109:
 
* What is the current version of the plug-in ?
 
* What is the current version of the plug-in ?
  
0.0.2
+
0.0.3
  
 
* What are the known bugs of the plug-in ?
 
* What are the known bugs of the plug-in ?

Revision as of 07:07, 20 September 2007

Student: Mariot Chauvin (IRC: moksha_anderson)

Mentors: Philippe Ombredanne (IRC: pombreda), Francois Granade (IRC: farialima)

This project is part of the Google Summer of Code 2007


Introduction

Eclipse is an extensible framework to build modular applications, which relies on OSGi component architecture. Originally developed to provide an IDE extensible in terms of functionalities and supported languages with plugins, Eclipse can now be used as a Rich Client Platform (RCP). The success of the Java Development Toolkit (JDT) plugin has lead to the development of numerous plugins. For instance the C/C++ Development Toolkit (CDT) plugin allows developers to use it as IDE for project in C or C++ language. The use of Eclipse as a generic IDE is possible due to the notion of perspective (a perspective corresponds to a certain disposition of the graphical elements) which adapts the user interface to the kind of project.

Java Native Interface (JNI) is a programming interface to call native methods or to embed java virtual machine in native applications. JNI is often used to interact with existing native application, to add platform-specific functions, or to improve time-performance (by supposing native methods faster than java code).

Currently, when users work on a java project using JNI and native code, they have to switch between perspective, which is not practical. Another point to improve is the debugging of this kind of project, by allowing developers to follow native method calls into native code and go back.

Goals of the project

  • Create new or 'mixed' perspectives to manage project using C/C++ and Java
  • Add the possibility to follow native methods calls into native code

Work done

First step : documentation of existing work

Second step : prototype

  • work on a prototype which
    • launch a Java Debugger
    • attach a C debugger to the JVM
    • allow you to debug C/C++ code and Java code debugging in the same view

Third step : tests and debugging

  • a first version is available to download (see below):
    • creation of JUnit tests
    • bugs hunt
    • advertisement and feedback from community


Roadmap

  • 0.0.4 - 15 October 2007 (planned)
    • jvm started in native code debugging
    • see ho integrate in eclipse CDT ?

Documentation

How to install the plug-in ?

The most simple is to use the update manager of Eclipse. Simply add this site as "new remote site" :

http://eclipse-incub.svn.sourceforge.net/viewvc/*checkout*/eclipse-incub/org.eclipse.soc.jni/update-site/site.xml

The sources are included in the Jar, but you can get them on the subversion repository:

https://eclipse-incub.svn.sourceforge.net/svnroot/eclipse-incub/org.eclipse.soc.jni

( You may have to install the subclipe plug-in )

How to use the plug-in ?

You should have some java code which uses JNI and the native code associated. The plug-in should be installed.

First step

Set a breakpoint in the Java code after the code which loads the native library.

Soc jni J breakpoint.png

Second step

Open the debug dialog and create a new configuration of "Java JNI Application" kind.

Soc jni Config group.png

Third step

Set the correct settings for each tab.

  • C/C++ project tab
    Set the C/C++ project and specify the javaw path as C/C++ application.
  • Java project tab
    Set the Java project and the main class.
Soc jni Config tab j main.png
  • Environment tab
    On linux machines you could have to add the current directory to the library path environment variable.


Fourth step

The debug perspective will be launched with the 2 debuggers. Ready to debug !

Soc jni Debug perspective.png

How to report a bug/ask for an enhancement ?

On the eclipse bugzilla there is a "org.eclipse.soc.jni" component for the "SOC" product in the "Technology" category. Please include the version of the plug-in and the maximum infos you can obtain.

FAQ

  • What is the current version of the plug-in ?

0.0.3

  • What are the known bugs of the plug-in ?

all bugs open bugs