How to enable debugging output

From mitk.org
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

BlueBerry applications usually support the following command line option for enabling debug output: 

--BlueBerry.debug [options file]

if set, the platform is put in debug mode. If the value is a string it is interpreted as the location of the .ctk.options file. This file indicates what debug points are available for a plug-in and whether or not they are enabled. If a location is not specified, the platform searches for the .ctk.options file under the install directory.

Debug points are plug-in specific. They can either be specified as framework properties or in the above mentioned .ctk.options file, using the INI format.

CTK Plugin Framework

The CTK Plugin Framework supports the following debug points

  • org.commontk.pluginfw/debug
  • org.commontk.pluginfw/debug/errors
  • org.commontk.pluginfw/debug/pluginfw
  • org.commontk.pluginfw/debug/hooks
  • org.commontk.pluginfw/debug/lazy_activation
  • org.commontk.pluginfw/debug/ldap
  • org.commontk.pluginfw/debug/service_reference
  • org.commontk.pluginfw/debug/startlevel
  • org.commontk.pluginfw/debug/url
  • org.commontk.pluginfw/debug/resolve

org.blueberry.core.expressions

The org.blueberry.core.expressions plug-in supports the following debug points

  • org.blueberry.core.expressions/tracePropertyResolving
  • org.blueberry.core.expressions/debug/TypeExtensionManager

org.blueberry.ui.qt

The org.blueberry.ui.qt plug-in supports the following debug points

  • org.blueberry.ui.qt/debug
  • org.blueberry.ui.qt/trace/dragDrop
  • org.blueberry.ui.qt/trace/perspectives
  • org.blueberry.ui.qt/debug/job.stale
  • org.blueberry.ui.qt/trace/sources
  • org.blueberry.ui.qt/trace/keyBindings
  • org.blueberry.ui.qt/trace/keyBindings.verbose
  • org.blueberry.ui.qt/trace/commands
  • org.blueberry.ui.qt/trace/contexts
  • org.blueberry.ui.qt/trace/contexts.performance
  • org.blueberry.ui.qt/trace/contexts.verbose
  • org.blueberry.ui.qt/trace/handlers
  • org.blueberry.ui.qt/trace/handlers.performance
  • org.blueberry.ui.qt/trace/handlers.verbose
  • org.blueberry.ui.qt/trace/operations
  • org.blueberry.ui.qt/trace/operations.verbose
  • org.blueberry.ui.qt/debug/showAllJobs
  • org.blueberry.ui.qt/debug/contributions
  • org.blueberry.ui.qt/trace/handlers.verbose.commandId=<command_id>
  • org.blueberry.ui.qt/debug/workingSets

Example debug file

This is an example .ctk.options file 

[org.commontk.pluginfw]
debug=1

[org.commontk.pluginfw/debug]
errors=1
pluginfw=1
hooks=1
lazy_activation=1
ldap=1
service_reference=0
startlevel=0
url=0
resolve=1

[org.blueberry.core.expressions]
tracePropertyResolving=1

[org.blueberry.core.expressions/debug]
TypeExtensionManager=1

[org.blueberry.ui.qt]
debug=1

[org.blueberry.ui.qt/trace]
dragDrop=1
perspectives=1
sources=1
keyBindings=1
keyBindings.verbose=1
commands=1
contexts=1
contexts.performance=1
contexts.verbose=1
handlers=1
handlers.performance=1
handlers.verbose=1
;handlers.verbose.commandId=my.command.id
operations=1
operations.verbose=1

[org.blueberry.ui.qt/debug]
job.stale=1
showAllJobs=1
contributions=1
workingSets=1
Retrieved from "http://mitk.org/w/index.php?title=How_to_enable_debugging_output&oldid=2584"