Update of /cvsroot/cpptool/rfta/src/eclipseplugin/PluginCode
In directory sc8-pr-cvs1:/tmp/cvs-serv25059/src/eclipseplugin/PluginCode
Modified Files:
PlugIn-HowTos.txt
Log Message:
-- updated developer infos
Index: PlugIn-HowTos.txt
===================================================================
RCS file: /cvsroot/cpptool/rfta/src/eclipseplugin/PluginCode/PlugIn-HowTos.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** PlugIn-HowTos.txt 15 Feb 2003 13:35:13 -0000 1.1
--- PlugIn-HowTos.txt 16 May 2003 08:27:45 -0000 1.2
***************
*** 27,41 ****
How to Debug ?
! Unfortunatly native code is a little bit critical since, the
! cpp code is running as DLL loaded by the JAVA-VM. If the
! DLL crashes, the complete JAVA-VM will be destroyed.
! For this reason "DebugBreak" does also not work at the moment.
! (It seems for me that java.exe has called some win-api function
! to redirect this exception handling. Can we change this for
! debugging ?)
! At the moment we need a very restrictive catching of all
! exceptions in C++. A not catched exception means destroying
! a running exclipse workbench (which is worse of cause).
We can throw Java-Exception using the JNI-Interface, so that
--- 27,37 ----
How to Debug ?
! DebugBreak does now work. Using this function it's possible to
! stop the execution of that plugin code within any dll-loaded by
! the java-vm. choose cancel to start the vc6 debugger.
! We need a very restrictive catching of all exceptions in C++.
! A not catched exception does destroy the complete exclipse
! workbench, which is worse of cause.
We can throw Java-Exception using the JNI-Interface, so that
***************
*** 44,51 ****
Maybe we introduce a specialized exception class later on.
! By the way: The Plugin and the DLL are loaded when the user
! activates a refactoring action the first time.
! What to do to run the debug mode showing a console:
- load the eclipse-plugin project into the workbench (call this debugging workbench)
- don't activate the plugin in this workbench !
--- 40,48 ----
Maybe we introduce a specialized exception class later on.
! By the way, the Plugin and the connected DLLs are loaded when
! the user activates a refactoring action the first time.
! What to do to run the plugin in eclipse debug mode
! showing a console:
- load the eclipse-plugin project into the workbench (call this debugging workbench)
- don't activate the plugin in this workbench !
|
