MATLAB: Does MATLAB 6.5 (R13) crash when the PRINT function is executed on a Red Hat Enterprise 3.0 or Fedora machine

-dtiffnocompressioncrashenterprisefedorahatlibclinuxMATLABprintred

MATLAB 6.5 (R13) produces a Segmentation Violation crash when the following call to the PRINT function is executed:
print(8,'-dtiffnocompression','test')
The segmentation violation produced is:
 ------------------------------------------------------------------------
        Segmentation violation detected at Fri Jun  4 12:36:22 2004
 ------------------------------------------------------------------------
 Configuration:
   MATLAB Version:   6.5.0.180913a (R13)
   Operating System: Linux 2.4.22-1.2188.nptlsmp #1 
 SMP Wed Apr 21 20:12:56 EDT 2004 i686
   Window System:    The XFree86 Project, Inc (40300000), display :2.0
   Current Visual:   0x22 (class 4, depth 16)
   Processor ID:     x86 Family 15 Model 2 Stepping 5, GenuineIntel
   Virtual Machine:  Java is not enabled
 Register State:
   eax = 000b48a8   ebx = 004c2238
   ecx = 087d43a0   edx = 004c2ba0
   esi = 000015c0   edi = 087d5960
   ebp = bfff32c0   esp = bfff326c
   eip = 003fd082   flg = 00210287
 Stack Trace:
   [0] libc.so.6:0x003fd082(0x004c2ba0, 0x087d43a8, 0xbfff3310, 4183827)
   [1] libc.so.6:0x003fd713(0x004c2ba0, 0x087d3cd8, 1736, 7312)
   [2] libc.so.6:__libc_realloc~(0x087d3cd8, 1736, 0xbfff3378, 0x40015e06) + 255 bytes
   [3] libut.so:mw_realloc(0x087d3ce0, 1728, 0xbfff33a8, 0x4001103a) + 143 bytes
   [4] libut.so:utRealloc(0x087d3ce0, 1728, 0xbfff33d8, 0x4002ef3e) + 102 bytes
   [5] libut.so:ut_mem_realloc(0xbfffdb30, 0x087d3ce0, 1728, 0x4002e883) + 58 bytes
   [6] libut.so:ut_initialize_lineno_map(0xbfff3698, 0xbfffdb30, 0x08805be8 "function imwrite(varargin)\n%IMW", 14566) + 467 bytes
   [7] libmwm_pcodegen.so:mpg_initialize_pcode_source_annotation(0xbfff367c, 0xbfffdb30, 0x08805be8 "function imwrite(varargin)\n%IMW", 14566) + 77 bytes
   [8] libmwm_interpreter.so:inCompileMfile(word *, char const *, bool, bool, _m_parser_interface *)(0x42797ad8, 0x4179e308

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 has been verified as a bug in MATLAB 6.5 (R13) in the way that the PRINT function is handled on some Red Hat Enterprise or Fedora machines.
There are currently no known workarounds.
Related Question