Why does my Simulink model, which ran in MATLAB 6.0 (R12), cause a segmentation violation when run in MATLAB 6.1 (R12.1)?

Why does my Simulink model which ran without error in MATLAB 6.0 (R12), cause the following segmentation iolation when run in MATLAB 6.1 (R12.1):

 ----------

 Segmentation iolation detected!

 ----------

 MATLAB ersion: 6.1.0.450 (R12.1)

 Operating System: Microsoft Windows NT

 Window System:ersion 4.0 (Build 1381: Serice Pack 6)

 Processor ID: x86 Family 6 Model 8 Stepping 6, GenuineIntel

 irtual Machine:Jaa 1.1.8 from Sun Microsystems Inc.

 Register State:

 EAX = 0000fffdEBX = 02ea9384

 ECX = 02ea8918EDX = e573f167

 ESI = 02f5ed70EDI = 00000001

 EBP = 0149bb50ESP = 0149bb40

 EIP = 01b5fc17FLG = 00010206

 Stack Trace:

 [0] simulink.dll:_AX_plus_BU(0x02f5ebe0, 0x02ea8920, 0x02ea9380, 0x02ea890c) + 71 bytes

 [1] simulink.dll:_StateSpaceDeriFcn(2, 0x02f5f380, 0x02f5eb88, 0x1cdde578) + 160 bytes

 [2] simulink.dll:_BlockDeri(0x00e70298, 0x140fe898, 0x1cdb2108, 0x02f5ed00) + 110 bytes

 [3] simulink.dll:_BdSystemDeriaties(0x140fe898, 0x03029530, 13, 0x140fe898) + 115 bytes

 [4] simulink.dll:_BdDerivFcn(0x03029530, 0x140feab8, 0x140fe898, 0x1cdb2108) + 61 bytes

 [5] simulink.dll:_UpdateContinuousStates(0x140feab8, 0x0149bc40, 0x01c39603, 0x140feab8) + 87 bytes

 [6] simulink.dll:_ModelUpdateContinuousStates(0x140feab8, 0x140fe898, 0x140feab8, 0) + 43 bytes

 [7] simulink.dll:_slIntegrate(1043128, 0, 0x02f61034, 0xffffffff) + 243 bytes

 [8] simulink.dll:_StepMenuSim(1043128, 0x1cc9dc48, 0x1cc9dc80, 0x77e7198f) + 392 bytes

 [9] uiw.dll:_UIW_CallWorkProcs(0x0149bd98, 0x1cc9dc48, 0x6c6f6f54, 0x57726162) + 105 bytes

 [10] uiw.dll:_getCommand(0x1cc9dc80, 4096, 255, 0x1cd97f28) + 108 bytes

 [11] matlab.exe:_ioReadLine(255, 0x78037c28, 0x1cd97f28, 4096) + 299 bytes

 [snip]

[13] matlab.exe:_mnParser(0x018ce198, 0x014a4eb2, 0, 39) + 922 bytes

[14] matlab.exe:_WinMain@16(4194304, 0, 0x014a4eb2, 1) + 3136 bytes

[15] matlab.exe:_WinMainCRTStartup(0x018ce198, 0x77c440e0, 0x7ffdf000, 0x7ffdf000)

Answer 1

[MathWorks Support Team]

This has been fixed in Simulink 4.1.1 (R12.1+).

If you are still using Simulink 4.1 (R12.1), you can try to run SLUPDATE on the model in MATLAB R12.1. For further information, please type 'help slupdate' at the MATLAB command prompt. Perhaps certain blocks are slightly different from the previous version of MATLAB, and this may be causing the crash.

In addition, you may try to build the model again in R12.1 to see if this corrects the problem.