MATLAB: Do I receive a Segmentation Violation when opening a model created with Simulink 6.1 (R14SP1) that contains a scope created with the Signal & Scope Manager

floatingscopesegmentationsegvsignalsimulinkviolation

I have a model containing a scope created by the Signal & Scope Manager. When I try to open the model from the MATLAB Command Prompt, I get the following Segmentation Violation:
 Configuration:
   MATLAB Version:   7.0.1.24704 (R14) Service Pack 1
   Operating System: Microsoft Windows XP
   Window System:    Version 5.1 (Build 2600: Service Pack 1)
   Processor ID:     x86 Family 15 Model 2 Stepping 9, GenuineIntel
   Virtual Machine:  Java 1.4.2_04 with Sun Microsystems Inc. Java HotSpot(TM)
 Register State:
   EAX = ec034b00  EBX = 7a2a459c
   ECX = 00cde2a8  EDX = 5d5be08a
   ESI = 00000000  EDI = 7a2a459c
   EBP = 00cde280  ESP = 00cde228
   EIP = 79fa7d70  FLG = 00010202
 Stack Trace:
   [0] simulink.dll:struct slErrMsg_tag * __cdecl UpdateReference(struct slBlock_tag *,struct slBlock_tag * *)(0x7a2a459c, 0x00cde2a8, 0, 0x2190a660) + 112 bytes
   [1] simulink.dll:struct slErrMsg_tag * __cdecl UpdateRefsAlongIOConnectivityPath(struct slBlock_tag const *,char const *)(0x2190a660, 1, 0, 2) + 91 bytes
   [2] simulink.dll:struct slErrMsg_tag * __cdecl ConvertPathStringsToPortPointers(struct slBlock_tag const *,int,char const * *,int const *,int const *,struct slPort_tag * * *)(0x2190a660, 1, 0x24381110 "ðñ/$mal", 0x00cde344) + 226 bytes
 ...

Best Answer

This bug has been fixed in Release 14 Service Pack 2 (R14SP2). For previous releases, please read below for any possible workarounds:
This problem can occur when you have blocks with a "/" in their names, whose output signals are being viewed by a scope or a floating scope. To work around this issue, please remove the "/" from your blocks name or view a signal that does not come from a block with a "/" in the name. You can open the model to make the changes by using the following command:
open('model_name.mdl')
instead of calling the model name from the Command Prompt.
Related Question