Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA/Query/DeveloperDocumentation/FeatureSetAndTesting/Debug"
m (Harmath.incquerylabs.com moved page EMFIncQuery/DeveloperDocumentation/FeatureSetAndTesting/Debug to VIATRA/Query/DeveloperDocumentation/FeatureSetAndTesting/Debug: Project merge) |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | __TOC__ | ||
+ | |||
=== Debugger Tooling === | === Debugger Tooling === | ||
Line 17: | Line 19: | ||
− | For more information | + | For more information see also [[EMFIncQuery/UserDocumentation/DebuggerTooling]] |
Latest revision as of 09:18, 10 March 2016
Contents
Debugger Tooling
The EMF-IncQuery debugger tooling aims to provide useful functionalities for the users, so that they can easily observe the contents of the EMF-IncQuery related artifacts when the program execution has stopped at a breakpoint. The plan is to provide three kinds of support for debugging:
- Possibility to explore the contents of the EMF instance models
- Navigation in the contents of EMF-IncQuery pattern matcher engines (matchers, matches, match parameters, etc)
- Navigation in the contents of EMF-IncQuery Rule Engines
Usage (run from source):
- launch runtime Eclipse from source (on host Eclipse)
- place brakepoint in code (e.g. in a @Test in the imported School example)
- note: generated projects can cause NoClassDefFoundErrors
- run required plugins (e.g. as JUnit-Plugin Test) in Debug Mode
- note: in special cases you can run your application in headless mode
For more information see also EMFIncQuery/UserDocumentation/DebuggerTooling