[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Hello,
Arnaud GIULIANI a écrit :
Hello William,
William Piers a écrit :
At this time, the emfvm doesn't have a debugger interface. So if you
want to rewrite your profiler for it, you will need to define a
debugger interface, as you made for the Regular VM (in this case you
"simply" extended the debugger interface, right ?).
We are very interested on seeing your contribution, then we will be
able to give you comments in order to help you defining the
debug/profiling interface... and later to integrate it into ATL.
For the Regular VM, I created a VM based on it and modified the
runAtlLauncher method to setup my profiler. I used the
AtlLauncher.launch method with my profiler in argument. In the EMF
specific VM, I haven't found where to add my profiler (no
AtlLauncher.launch method used ?!). Can you help understand how the
ATL execution is launched fro this VM ?
At this time the emfvm is launched using dependently of
org.eclipse.m2m.atl.debug (see class
/org.eclipse.m2m.atl.engine.emfvm/src/org/eclipse/m2m/atl/engine/emfvm/AtlEMFSpecificVM.java).
This solution will probably change in the future, so you better have to
inspirate from this code :
/org.eclipse.m2m.atl.examples/src/org/eclipse/m2m/atl/examples/EMFVMLauncher.java
Those launching facilities will be soon refactored in order to provide
them directly in the VMs. The last class I reference is a kind of
temporary "workaround" so I advise you to copy it into your solution
instead of make a dependency on org.eclipse.m2m.atl.examples. At least
this class (or a better interface) will be integrated in an other plugin.
Best regards,
William
Regards,
Arnaud GIULIANI.
_______________________________________________
m2m-atl-dev mailing list
m2m-atl-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-atl-dev
begin:vcard
fn:William Piers
n:Piers;William
org:Obeo
adr:2 rue Robert Schumann;;lot 24;NANTES;;44408;France
email;internet:william.piers@xxxxxxx
title:MDA Consultant
tel;work:+33 (0)2 51 13 51 82
tel;cell:+33 (0)6 20 31 75 98
url:http://www.obeo.fr
version:2.1
end:vcard