Stateflow

Overview of the Stateflow Debugger

Use the Stateflow debugger to evaluate code coverage and perform dynamic checking during simulation to ensure that your Stateflow diagrams are behaving exactly as you expect them to.

Note    Generally speaking, debugging options should be disabled for Real-Time Workshop and stand-alone targets. The Debugger does not interact with Real-Time Workshop or stand-alone targets and the overhead incurred from the added instrumented code is undesirable.

This section contains the following topics:

• Typical Debugging Tasks -- Lists some of the debugging tasks you want to accomplish with the Debugger during simulation.
• Including Error Checking in the Target Build -- Shows you the options that you can add to generated code for your target to help you debug your application.
• Breakpoints -- Lists execution points that you can specify in your target where execution stops for debugging purposes.
• Run-Time Debugging -- Lists debugging options that you can enable and disable during simulation.

Note    When you save the Stateflow diagram, all the Debugger settings (including breakpoints) are saved.

Typical Debugging Tasks

These are some typical debugging tasks you might want to accomplish:

• Animate Stateflow diagrams, set breakpoints, and debug run-time errors
• Evaluate coverage
• Check for errors involving the following:
• State inconsistencies
• Conflicting transitions
• Data range violations
• Cyclic behavior

Debugging and Testing

Including Error Checking in the Target Build