MATLAB: Do I receive a segmentation violation when I call the BUILTIN command without any inputs in MATLAB 7.0 (R14)

builtinMATLABsegmentationsegvviolation

If I use the command:
builtin
I receive the following segmentation violation:
------------------------------------------------------------------------
Segmentation violation detected at Fri Jul 09 15:20:36 2004
------------------------------------------------------------------------
Configuration:
MATLAB Version: 7.0.0.19920 (R14)
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 with Sun Microsystems Inc. Java HotSpot(TM) Client VM
(mixed mode)
Default Charset: ibm-5348_P100-1997
Register State:
EAX = 7880b500 EBX = 00cde434
ECX = 00000000 EDX = 0125a4c8
ESI = 00cde0f4 EDI = 00000000
EBP = 00cde0c8 ESP = 00cde0c0
EIP = 787f4205 FLG = 00010206
Stack Trace:
[0] mvalue.dll:public: class Mprotected_cptr<char const ,&char const * __cdecl mvCopyString(char const *),&void __cdecl mvFreeString(char const *)> __thiscall Mimplementation::tomvString(void)const (0x00cde0f4, 0x0e5ef220, 0, 0x00cde108 "¨äÍ") + 69 bytes
[1] m_dispatcher.dll:public: class Mprotected_cptr<char const ,&char const * __cdecl mvCopyString(char const *),&void __cdecl mvFreeString(char const *)> __thiscall Mvalue_common<class Mimplementation>::tomvString(void)const (0x00cde0f4, 0, 0x012d6740, 0) + 22 bytes
[2] m_dispatcher.dll:_mdBuiltinAsBuiltinFcn(0, 0x00cde27c "0áÍ", 0, 0x00cde434) + 50 bytes
<snip>

Best Answer

This bug has been fixed for Release 14 SP1 (R14SP1). For previous releases, please read below for any possible workarounds:
We have verified there is a bug in the BUILTIN function in MATLAB 7.0 (R14). This function should not run when used with no inputs.
The BUILTIN function without any input arguments is improper syntax. It should always receive at least one input, such as the name of the built-in function to call.