|
|
|
| R2012a Documentation → SimEvents | |
Learn more about SimEvents |
|
| Contents | Index |
| On this page… |
|---|
To end the debugger session without completing the simulation, enter one of these commands at the sedebug>> prompt:
sedb.quit
quit
The simulation ends, the debugging session ends, and the MATLAB command prompt returns.
At the sedebug>> prompt, quit is equivalent to sedb.quit. However, specifying the sedb package prevents you from inadvertently ending the MATLAB session if you enter the command at the incorrect command prompt.
The functions in the next table have different behavior and purposes, but any of the functions can cause the debugger session to end.
| Function | Behavior with Respect to Ending the Debugger Session | Primary Usage |
|---|---|---|
| sedb.quit or quit | Ends the debugger session without completing the simulation. | To end the debugger session immediately without spending time on further simulation log entries, plots, or other simulation behavior. |
| runtoend | Completes the simulation and then ends the debugger session. | To see the simulation log or plots but not enter commands. |
| cont | Ends the debugger session only if the simulation is suspended at the built-in breakpoint at the end of the simulation. | Primarily with breakpoints. For more information, see Using Breakpoints During Debugging. |
| step | Ends the debugger session only if the simulation is suspended at the built-in breakpoint at the end of the simulation. | Primarily for proceeding step by step through the simulation. For more information, see Stepping Through the Simulation. |
 | Independent Operations and Consequences in the Debugger | Stepping Through the Simulation |  |
Model electronic system architectures, process flows, and logistics as queuing systems or agent-based systems.
Get free kit| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |