Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [qvto-dev] QVT* Debug test framework
Hi Ed,
 
I think you can look at the implementation of debug VM (QVTOVirtualMachine class). This is quite generic concept which is used both for QVTO workspace and remote debuggers.

QVTo debugger itself exploits QVTODebugEvaluator which simply extends QvtOperationalEvaluationVisitor with debug-specific events handling, lines information, etc.
Debugger is executed by means of QVTODebugTarget class which uses QVTOVirtualProcess and QVTOThread classes. It utilizes concept of request-response to interoperate with debug VM.

Workspace debugger is launched by QVTODebugConfiguration and remote debugger is launched by QVTOApplicationConfiguration.
All source code resides in 'org.eclipse.m2m.qvt.oml.debug.core' plug-in.
Debug UI plug-in 'org.eclipse.m2m.qvt.oml.debug.ui' contains UI aspects of debugging support: breakpoints, watch view, UI for debug launch configuration, etc.
 
Regards,
  Sergey.

 

 



On Sun, May 19, 2013 at 10:07 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi Sergey

I notice some recent commits on debugging.

Now that we have QVTi CG going, I'm rethinking the order in which I write debuggers.

OCL is very troublesome since it has no natural activatiion, and validation wants to be in the invoking workspace, whereas QVTi is amenable to a simple remote activation.

So I now plan to do QVTi extensible to QVTc/QVTr as a conventional remote debugger then see how to localize the remote to support OCL vlidation debug later.

Any clues on bits of QVTo to look at exploit/what to rework to try to create something that is tailored for QVTo/QVTi/QVTc/QVTr/.... ?

    Regards

        Ed Willink


_______________________________________________
qvto-dev mailing list
qvto-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/qvto-dev

Back to the top