Read the debug configuration into the debug type 'me'
The debug definition is placed in the main level of the musubi.lua file
It can look like
debug={debugMode=true,-- default= false-- Use a logging object to track output in individual files.-- The output messages to this logging object are usually-- generated by tem_debug calls.logging={level=1,-- how detailed should the log be?filename='dbg',-- to which file to write the logroot_only=.false.}-- should only root write msgs?debugFiles=true,-- default= false-- What to dump into debugFiles? --dumpTreeIDs=true,-- default= falsedumpPropBits=true,-- default= falsedumpAuxLists=true,-- default= falsedumpDependencies=true,-- default= falsedumpState=true,-- default= falsedumpHaloState=true,-- default= false-- end debugFiles --debugDependencies=true,-- default= falsecheckDependencies=true,-- default= falsecheckNans=true,-- default= falsecheckSteps=true,-- default= falsedebugMesh='dbg/mesh_',-- default= ''debugSource=true,-- default= falsedebugRestart=true,-- default= falsetraceMemory=true,-- default= false}
Possible Options are
- active = {true, false}\n
activate or deactivate the complete debug mode. If deactivated, all
subsequent definitions are ignored
Todo
: Check the following reference
- [[tem_debug_module:tem_debug_type.debugFiles]] = {true, false}
open debug files. They can be accessed by writing to the unit dbgUnit.
the dbgUnit is given in the tem_debug_module and simply needs to be included
into the use statements
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.