Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "VIATRA/Query/DeveloperDocumentation/FeatureSetAndTesting/Debug"

Line 6: Line 6:
 
* Navigation in the contents of EMF-IncQuery pattern matcher engines (matchers, matches, match parameters, etc)
 
* Navigation in the contents of EMF-IncQuery pattern matcher engines (matchers, matches, match parameters, etc)
 
* Navigation in the contents of EMF-IncQuery Rule Engines
 
* 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
 +
 +
[[File:Emf incquery debugger tooling.PNG|900px]]
 +
  
 
For more information visit: [[https://wiki.eclipse.org/EMFIncQuery/UserDocumentation/DebuggerTooling More]]
 
For more information visit: [[https://wiki.eclipse.org/EMFIncQuery/UserDocumentation/DebuggerTooling More]]

Revision as of 06:04, 31 March 2015

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):

  1. launch runtime Eclipse from source (on host Eclipse)
  2. place brakepoint in code (e.g. in a @Test in the imported School example)
    • note: generated projects can cause NoClassDefFoundErrors
  3. run required plugins (e.g. as JUnit-Plugin Test) in Debug Mode
    • note: in special cases you can run your application in headless mode

Emf incquery debugger tooling.PNG


For more information visit: [More]

Back to the top