Use the Command History or the file on which it is based, history.m, to run statements from the previous session. You might be able to recreate data as it was before the termination.

If you used the diary function or -logfile startup option for the session in which MATLAB terminated unexpectedly, then you might be able to recover output.

If you saved the workspace to a MAT-file during the session, then you can recover it by loading the MAT-file.

If you were editing a file in the Editor when MATLAB terminated unexpectedly, and you had the backup feature enabled, then you should be able to recover changes you made to files you had not saved. To recover, open the backup version filename.asv in the Editor. Then save it as filename.m to use the last good version of filename.

If you were in a Simulink^® session when a segmentation violation occurred, and you have the Simulink Autosave Options preference selected, then the last autosave file for the model reflects the state of the autosave data before the segmentation violation. Because Simulink models might be corrupted by a segmentation violation, a model is not autosaved after a segmentation violation occurs. To recover the file, open the model.