Debug console output

The following types of debug output are available:

Debug the CIF/SVG declarations [svg]

Prints debugging information to the console, for the CIF/SVG declarations. For more information on this kind of debugging output, see the page on console debugging for CIF/SVG declarations.

Debug the parser [parser]

Prints debugging information to the console, for the parser. This information is primarily intended for the developers of the simulator, and not for end users.

Debug the generated code (by writing it to disk) [gen-code]

The simulator generates highly optimized code for the specification. Enabling this debugging output, writes the generated code to disk, for further debugging. This information is primarily intended for the developers of the simulator, and not for end users.

Debug the ODE solver [ode]

Prints debugging information to the console, for the ODE solver. This information can for instance be used to figure out why a state event (guard change) was missed.

Debug output option

In the option dialog, each of the different types of output can be enabled and disabled individually (Debug output option, Output category).

From the command line, using the -d or --debug option, the names of the different types of debug output, as specified between square brackets, should be used, separated by commas. By default, i.e. when not using the -d or --debug option, all debug output is disabled. As an example, consider -d parser,svg or --debug=parser,svg. Debug output is printed for the parser (due to parser) and CIF/SVG declarations (due to svg).

Specifying an output type twice leads to a warning being printed to the console.

Enabling any debug output, automatically changes the output mode to ‘debug mode’.

Profiling

If profiling is enabled, all debug output is automatically disabled. That is, profiling suppresses all debug output.

Version r9682. Copyright © 2012-2016, Eindhoven University of Technology. Created using Sphinx 1.2.2.