Eclipse Community Forums: M2M (model-to-model transformation)

Help

Home

Home » Archived » M2M (model-to-model transformation) » [Xtend] Debugging Irritation

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

[Xtend] Debugging Irritation [message #523849]

Mon, 29 March 2010 15:39

Ludwig Straub

Messages: 14
Registered: July 2009

Junior Member

Hello,
(I hope this ist the correct location for my question.)

I'm running a M2M Transformation from a ecore model (created via Xtext) using Xtend (Helios M6) and a mwe (not mwe2) workflow.

All works fine and the result is just as it is mentioned to be.
Unfortunately I am not able to get the debugger running in a predictable way.

If I try to enable a breakpoint by double-clicking on the bar left of the Xtend-editor, sometimes no breakpoint occurs and sometimes the breakpoint is moved to the first line of code of the file but not where it was meant to be. I am then however able to step forward to the desired line of code, even if it is located within a deep sub-method.

Another issue I came across is that the debbugger crashes whenever I try to pass a input parameter to the workflow (via the -p or --param option).

Console output:

0    ERROR WorkflowRunner     - 
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.emf.mwe.core.WorkflowRunner.main(WorkflowRunner.java:207)
Caused by: java.io.IOException: Couldn't establish connection to Debugger on port 0
	at org.eclipse.emf.mwe.internal.core.debug.processing.DebugMonitor.init(DebugMonitor.java:82)
	... 5 more

If I run the same configuration without debugging, all works fine:

0    INFO  WorkflowRunner     - --------------------------------------------------------------------------------------
16   INFO  WorkflowRunner     - EMF Modeling Workflow Engine 1.0.0, Build v201003150825
16   INFO  WorkflowRunner     - (c) 2005-2009 openarchitectureware.org and contributors
16   INFO  WorkflowRunner     - --------------------------------------------------------------------------------------
16   INFO  WorkflowRunner     - running workflow: XXXXX.mwe
...

What could be the reason for these problems?
My eclispe installation is rather plain, based on the modelling distribution. I just added subclipse and Xtext support so far.

Thanks a lot in advance!

Ludwig

Report message to a moderator

Re: [Xtend] Debugging Irritation [message #524483 is a reply to message #523849]

Thu, 01 April 2010 07:00

Sebastian Zarnekow

Messages: 3118
Registered: July 2009

Senior Member

Hi Ludwig,

the observed behavior clearly indicates some bugs in the debugging
support of Xpand. Would you please be so kind and file new tickets for
the issues that have not yet been filed as a bugzilla?

Thanks,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 29.03.10 17:39, schrieb Ludwig Straub:
> Hello,
> (I hope this ist the correct location for my question.)
>
> I'm running a M2M Transformation from a ecore model (created via Xtext)
> using Xtend (Helios M6) and a mwe (not mwe2) workflow.
>
> All works fine and the result is just as it is mentioned to be.
> Unfortunately I am not able to get the debugger running in a predictable
> way.
>
> If I try to enable a breakpoint by double-clicking on the bar left of
> the Xtend-editor, sometimes no breakpoint occurs and sometimes the
> breakpoint is moved to the first line of code of the file but not where
> it was meant to be. I am then however able to step forward to the
> desired line of code, even if it is located within a deep sub-method.
>
>
> Another issue I came across is that the debbugger crashes whenever I try
> to pass a input parameter to the workflow (via the -p or --param option).
>
> Console output:
>
> 0 ERROR WorkflowRunner - java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.emf.mwe.core.WorkflowRunner.main(WorkflowRunner. java:207)
> Caused by: java.io.IOException: Couldn't establish connection to
> Debugger on port 0
> at
> org.eclipse.emf.mwe.internal.core.debug.processing.DebugMoni tor.init(DebugMonitor.java:82)
>
> ... 5 more
>
>
> If I run the same configuration without debugging, all works fine:
>
> 0 INFO WorkflowRunner -
> ------------------------------------------------------------ --------------------------
>
> 16 INFO WorkflowRunner - EMF Modeling Workflow Engine 1.0.0, Build
> v201003150825
> 16 INFO WorkflowRunner - (c) 2005-2009 openarchitectureware.org and
> contributors
> 16 INFO WorkflowRunner -
> ------------------------------------------------------------ --------------------------
>
> 16 INFO WorkflowRunner - running workflow: XXXXX.mwe
> ...
>
>
>
> What could be the reason for these problems?
> My eclispe installation is rather plain, based on the modelling
> distribution. I just added subclipse and Xtext support so far.
>
>
> Thanks a lot in advance!
>
> Ludwig

Report message to a moderator