Eclipse Community Forums: ATL » ATL Debug Mode Working?

Help

Home

Home » Modeling » ATL » ATL Debug Mode Working?

Show: Today's Messages :: Show Polls :: Message Navigator

ATL Debug Mode Working? [message #1417370]

Fri, 05 September 2014 09:21

Ronan B

Messages: 273
Registered: July 2009

Senior Member

Hi,
Does the ATL debug mode work at all? I'm using the EMF Specific VM with ATL 3.5 and execution never stops at my breakpoints.
Regards,
Ronan

Report message to a moderator

Re: ATL Debug Mode Working? [message #1418195 is a reply to message #1417370]

Sat, 06 September 2014 17:53

Hamid Qartal

Messages: 33
Registered: December 2013

Member

Hi,

Are you putting breakpoints on the target pattern elements! ATL Debugging as stated in the following documents does not stop in all the break points you are putting inside your code. Consult the following document for further information.

http://www.eclipse.org/atl/documentation/old/ATL_User_Manual[v0.7].pdf

Hope this helps

[Updated on: Sat, 06 September 2014 17:55]

Report message to a moderator

Re: ATL Debug Mode Working? [message #1418845 is a reply to message #1418195]

Sun, 07 September 2014 18:59

Dennis Wagelaar

Messages: 589
Registered: September 2012
Location: Belgium

Senior Member

op 06-09-14 19:53, Hamid Qartal schreef:
> Hi,
>
> Are you putting breakpoints on the target pattern elements! ATL Debugging as
> stated in the following documents does not stop in all the break points you
> are putting inside your code. Consult the following document for further
> information.
>
> http://www.eclipse.org/atl/documentation/old/ATL_User_Manual[v0.7
>
> Hope this helps

Also, the standard ATL VM requires you to put the breakpoints not on a *line*,
but on an *AST node* selected in the outline view: right-click AST node ans
select "Toggle Breakpoint".

See also https://wiki.eclipse.org/ATL/User_Guide_-_The_ATL_Tools#Outline

The EMFTVM adds support for regular *line* breakpoints, but there has to be
actual code on that line, or nothing happens. There is no up-front validation
that your breakpoint matches anything, like in Java.

Cheers,
Dennis

Report message to a moderator

Re: ATL Debug Mode Working? [message #1419205 is a reply to message #1418845]

Mon, 08 September 2014 08:51

Ronan B

Messages: 273
Registered: July 2009

Senior Member

Hi,
Ok thanks. I see the issue now. ATL doesn't switch perspective when the breakpoint is hit so it is easy to think nothing happened. So if I'm in the ATL perspective when I run the configuration the Debug perspective will *not* pop up. Should I file this as a bug/enhancement?

Also if I'm running 2 Eclipses for plugin development my breakpoints are never hit in the first Eclipse instance. So for example if I write ATL that will live in a plugin, surely the most likely development practice for any serious transformation, I cannot dubug the ATL in the plugin when the transformation is started in the second Eclipse. This makes debuging really tough as I must recreate my transforms in a single Eclipse instance environment. Is this also a bug or is there a work around?
Thanks!
Ronan

Report message to a moderator

Re: ATL Debug Mode Working? [message #1419571 is a reply to message #1419205]

Mon, 08 September 2014 20:27

Dennis Wagelaar

Messages: 589
Registered: September 2012
Location: Belgium

Senior Member

op 08-09-14 10:51, Ronan B schreef:
> Hi,
> Ok thanks. I see the issue now. ATL doesn't switch perspective when the
> breakpoint is hit so it is easy to think nothing happened. So if I'm in the
> ATL perspective when I run the configuration the Debug perspective will *not*
> pop up. Should I file this as a bug/enhancement?

This issue has been known for a while, but I can't find any bug on it. So yes,
please report it as a bug :-).

>
> Also if I'm running 2 Eclipses for plugin development my breakpoints are never
> hit in the first Eclipse instance. So for example if I write ATL that will
> live in a plugin, surely the most likely development practice for any serious
> transformation, I cannot dubug the ATL in the plugin when the transformation
> is started in the second Eclipse. This makes debuging really tough as I must
> recreate my transforms in a single Eclipse instance environment. Is this also
> a bug or is there a work around?
> Thanks!
> Ronan

This is possible. Your plugin will have to launch the ATL transformation in
debug mode, however. See AtlLaunchConfigurationDelegate and EMFVMUILauncher
for example code on how to do this:

http://git.eclipse.org/c/mmt/org.eclipse.atl.git/tree/plugins/org.eclipse.m2m.atl.core.ui/src/org/eclipse/m2m/atl/core/ui/launch/AtlLaunchConfigurationDelegate.java

http://git.eclipse.org/c/mmt/org.eclipse.atl.git/tree/plugins/org.eclipse.m2m.atl.engine.emfvm.launch/src/org/eclipse/m2m/atl/engine/emfvm/launch/EMFVMUILauncher.java

....or their EMFTVM counterpart:

http://git.eclipse.org/c/mmt/org.eclipse.atl.git/tree/plugins/org.eclipse.m2m.atl.emftvm.launcher/src/org/eclipse/m2m/atl/emftvm/launcher/EMFTVMLaunchConfigurationDelegate.java

ATL's default debugger port is 6060. You can connect to a running ATL VM in
debug mode using a "Remote ATL Transformation" debug launch configuration.

Cheers,
Dennis

Report message to a moderator