Why do I receive a segmentation violation when I run a model containing a Signal Viewer looking at signals in a configurable subystem in Simulink 6.2 (R14SP2)?

I have a model with several configurable subsystems. If I look at signals inside those subsystems with a Signal Viewer, I receive a segmentation violation like the following:

 ------------------------------------------------------------------------

        Segmentation violation detected at Tue Jun 14 09:56:01 2005

 ------------------------------------------------------------------------

 Configuration:

   MATLAB Version:   7.0.4.365 (R14) Service Pack 2

   Operating System: Microsoft Windows 2000

   Window System:    Version 5.0 (Build 2195: Service Pack 3)

   Processor ID:     x86 Family 15 Model 2 Stepping 9, GenuineIntel

   Virtual Machine:  Java 1.5.0 with Sun Microsystems Inc. Java HotSpot(TM) Client VM

     (mixed mode)

   Default Charset:  ibm-5348_P100-1997

 Register State:

   EAX = 00000000  EBX = 00000000

   ECX = 00000000  EDX = 01ad00f8

   ESI = 344479c0  EDI = 344463e0

   EBP = 00cdb034  ESP = 00cdb014

   EIP = 79dfbc68  FLG = 00210246

 Stack Trace:

   [0] simulink.dll:public: __thiscall slplRegInfo::slplRegInfo(class slplRegInfo const &)(0x344463e0 "@Û,.@1E4", 0x24919300 "ÄX\nzè³Û'", 0x24919314, 0x2494bba0) + 200 bytes

   [1] simulink.dll:public: __thiscall slplSigListInfo::slplSigListInfo(class slplSigListInfo const &)(0x28284160, 0x24913cc0, 0, 0x24913d60) + 154 bytes

   [2] simulink.dll:public: __thiscall PortLogResults::PortLogResults(class PortLogResults const &)(0x2494bba0, 0x34453760, 0x01d07490, 0) + 212 bytes

   [3] simulink.dll:public: __thiscall PortLogResults::PortLogResults(class PortLogResults const &)(0x24913d60, 0x1eff3200, 0x01d07490, 0) + 430 bytes

   [4] simulink.dll:void __cdecl SVUpdateOldBuffer(struct slBlock_tag *)(0x34453760, 0x1eff3200, 0x23dc34a0, 0) + 181 bytes

   [5] simulink.dll:struct slErrMsg_tag * __cdecl SVScopeTerminateFcn(struct slBlock_tag *,struct slSimBlock_tag *)(0x1eff3200, 0x23dc34a0, 0x23dc34a0, 0x1e650020) + 143 bytes

[snip]

Answer 1

[MathWorks Support Team]

This bug has been fixed in Release 2006a (R2006a). For previous product releases, read below for any possible workarounds:

There is a bug in Simulink 6.2 (R14SP2) when using a Signal Viewer with a configurable subsystem.

To work around the issue, you can enable signal logging by opening the model window and going to Simulation -> Configuration Parameters -> Data Import/Export and checking the 'Signal logging' box.