Debugging

By default, OSVVM scripts are set up to run regressions fast. Debugging information, logged signals and waveforms slow simulations down, so they are off. And if a simulation fails, the build goes on with the next one.

All settings below are booleans: true or false. Called without an argument, a Set* command means true.

Debug Mode

SetDebugMode adds the simulator’s debugging options to analyze and simulate, so signals and variables can be inspected. The default is false. GetDebugMode returns the setting.

SetDebugMode true

Logging Signal Values

SetLogSignals logs the values of signals during the simulation, so they can be displayed in the simulator’s waveform viewer after it finished. The default is false. GetLogSignals returns the setting.

For GHDL and NVC, which have no waveform viewer, see Saving Waveforms with GHDL and NVC.

SetLogSignals true

Stop on Errors

The variables AnalyzeErrorStopCount and SimulateErrorStopCount decide when a build stops: after that many analyze or simulate errors. 0, the default, means never; the build runs to its end.

# Stop at the first error
set ::osvvm::AnalyzeErrorStopCount  1
set ::osvvm::SimulateErrorStopCount 1

Interactive Mode

SetInteractiveMode does all of the above in one step:

the error stop counts become 1; switching back restores their previous values;
debug mode and signal logging follow the interactive mode, unless SetDebugMode or SetLogSignals set them explicitly.

In interactive mode, a build doesn’t exit the simulator even if the setting ExitOnBuildDone is true, and with the setting OpenBuildHtmlFile it opens the build report when it finishes. GetInteractiveMode returns the setting.

SetInteractiveMode
build ../RunExample.pro

SetInteractiveMode false