MATLAB: Do I get a segmentation violation when I try to open an empty custom library in Simulink 6.0 (R14)

browsercustomemptylibraryloadsimulink

I have an empty custom library defined by an slblocks.m file. When I open Simulink, the library appears in the browser. However, once I click on the "+" sign next to my custom library, I get the following error:
 ------------------------------------------------------------------------
        Segmentation violation detected at Fri Sep 03 11:40:58 2004
 ------------------------------------------------------------------------
 <snip>
 Stack Trace:
   [0] simulink.dll:private: void __thiscall CLibraryBrowser::UpdateBrowserNode(struct _TREEITEM *,struct mxArray_tag *)(437272, 0, 0x00cdaddc, 0x094e5e08) + 213 bytes
   [1] simulink.dll:private: void __thiscall CLibraryBrowser::LoadBrowserLibrary(struct _TREEITEM *)(0x081f1c08 "f-Logical Blocks", 0x094e5e08, 0x094e5e08, 78) + 391 bytes
   [2] simulink.dll:public: virtual int __thiscall CLibraryBrowser::OnNotify(unsigned int,long,long *)(0, 0x00cdaddc, 0x00cdab60, 0x094e5e08) + 269 bytes
   [3] MFC71.DLL:0x7c156147(78, 0, 0x00cdaddc, 0x00cdab8c)
   [4] MFC71.DLL:0x7c16e0b0(78, 0, 0x00cdaddc, 0x00cdacb0)
   [5] MFC71.DLL:0x7c16e14f(0, 2294606, 78, 0)
   [6] MFC71.DLL:0x7c16e1b8(2294606, 78, 0, 0x00cdaddc)
   [7] simulink.dll:long __stdcall AfxWndProcDllStatic(struct HWND__ *,unsigned int,unsigned int,long)(2294606, 78, 0, 0x00cdaddc) + 46 bytes
   [8] USER32.dll:0x77d43a50(0x7a282999, 2294606, 78, 0)
   [9] USER32.dll:0x77d43b1f(0, 0x7a282999, 2294606, 78)
   [10] USER32.dll:0x77d45453(0x00d35448, 0x00d353e0 "xSn¼EE", 0, 0x00cdaddc)
   [11] USER32.dll:0x77d454b4(2294606, 78, 0, 0x00cdaddc)
   [12] COMCTL32.dll:0x773456f8(432000, 0xfffffe3a, 0x00cdaddc, 432000)
   [13] COMCTL32.dll:0x773604e9(432000, 0xfffffe3a, 437272, 2)
   [14] COMCTL32.dll:0x7736045c(432000, 2, 2, 1)

Best Answer

This bug has been fixed in Release 14 Service Pack 3 (R14SP3). For previous product releases, read below for any possible workarounds:
This bug has been fixed in Release 14 Service Pack 2 (R14SP2). For previous releases, please read below for any possible workarounds:
This problem has been fixed in Simulink 6.1 (R14SP1). If you are using a previous version, read the following:
We have verified that there is a bug in Simulink 6.0 (R14) in the way that the library browser handles empty libraries. There are currently no known workarounds.
Related Question