| | 1 | = Options when instanciating MutekS = |
| | 2 | |
| | 3 | == Verbosity == |
| | 4 | |
| | 5 | DsxLogging facility will output log messages only if more important than current selected level. You may override this level by setting verbosity e.g.: |
| | 6 | {{{ |
| | 7 | muteks = MutekS( verbosity = "TRACE" ) |
| | 8 | }}} |
| | 9 | |
| | 10 | == Stack usage tracing == |
| | 11 | |
| | 12 | MutekS has fixed limited stack depth for all functions (defined at [wiki:DsxTaskModel#SoftwareTask software task implementation] declaration). Rather than trying different values and watching your software crash, you may want to put a big stack space, and watch which part of the available space was actually used. This can be archieved setting `STACK_TRACE` flag: |
| | 13 | |
| | 14 | {{{ |
| | 15 | muteks = MutekS( features = [ "STACK_TRACE" ] ) |
| | 16 | }}} |
