Unreachable execution path

Description

Select the diagnostic action to take when there are chart constructs not on a valid execution path. These constructs can cause unreachable execution paths:

• Dangling transitions not connected to a destination state, junction, or port

  

• Transition shadowing caused by an unconditional transition that prevents other transitions from the same source from executing

  

• States, junctions, or ports not connected with a transition from a reachable source

  

• Unconditional transitions leading out of a state that prevent the execution of the during actions in the state and the transitions between child states

  

Category: Diagnostics

Settings

Default: warning

none

No warning or error appears.

warning

A warning appears.

error

An error appears and stops the simulation.

Tip

This diagnostic does not detect unreachable execution paths caused by transition conditions that are always true or false. For example, in this chart, the diagnostic does not detect that the unconditional transition to state D is never valid.

If you have Simulink^® Design Verifier™, you can use dead logic detection to analyze your chart for this type of unreachable execution path. For more information, see Dead Logic Detection (Simulink Design Verifier).

Command-Line Information

Parameter: SFUnreachableExecutionPathDiag

Value: 'none' | 'warning' | 'error'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	warning
Traceability	No impact
Efficiency	No impact (for simulation) none (for production code generation)
Safety precaution	error

Related Topics

• Model Configuration Parameters: Stateflow Diagnostics
• Detect Modeling Errors During Edit Time (Stateflow)
• Dead Logic Detection (Simulink Design Verifier)