After starting MATLAB 7.0.4 (R14SP2) from the Windows command prompt, I receive a segmentation violation when I attempt to start MATLAB Report Generator 2.2.1 (R14SP2). To reproduce this behavior:
1. Goto the Windows Start menu and select "Run…"
2. Enter "command".
3. Enter "call matlab".
4. Enter the following MATLAB command:
report
I receive a segmentation violation with the following partial stack trace:
<snip> [0] MSVCR71.dll:0x7c3428d6(0, 4010688, 0xffffffff, 0) [1] bridge.dll:void __cdecl nmFullVerFcn(int,struct mxArray_tag * * const,int,struct mxArray_tag * * const)(0, 0x00cd8fcc, 1, 0x00cd902c) + 241 bytes [2] m_dispatcher.dll:public: virtual void __thiscall Mfh_builtin<struct mxArray_tag>::dispatch_mf(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00cd8fcc, 1, 0x00cd902c) + 55 bytes [3] m_dispatcher.dll:public: virtual void __thiscall Mfh_MATLAB_fn::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00cd8fcc, 1, 0x00cd902c) + 200 bytes [4] m_interpreter.dll:int __cdecl mdDispatch(int,char const *,int,struct mxArray_tag * *,int,struct mxArray_tag * *,class Mfh_MATLAB_fn * *)(38, 0x0dcc1844 "version", 0, 0x00cd8fcc) + 88 bytes [5] m_interpreter.dll:_inDispatchFromStack(38, 0x0dcc1844 "version", 0, 1) + 801 bytes [6] m_interpreter.dll:enum opcodes __cdecl inDispatchCall(char const *,int,int,int,int *,int *)(0x0dcc1844 "version", 38, 0, 1) + 138 bytes [7] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(0, 0, 0, 0) + 2434 bytes [8] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(0, 0, 0, 0) + 272 bytes [9] m_interpreter.dll:_inInterPcode(0, 0x78444d74, 0, 0) + 69 bytes </snip>
Best Answer