MPlayer 0.90pre5-3.1 (C) 2000-2002 Arpad Gereoffy (see DOCS!)

CPU: Intel Celeron 2/Pentium III Coppermine,Geyserville (Family: 6, Stepping: 6)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 0
Compiled for x86 CPU with extensions: MMX MMX2 SSE

Reading /home/q127038/.mplayer/codecs.conf: can't open '/home/q127038/.mplayer/codecs.conf': No such file or directory
Reading /share/caefs1/GNU/RedHat-7.1/usr/local///share/mplayer/codecs.conf: 34 audio & 94 video codecs
Linux RTC init error in ioctl (rtc_pie_on): Permission denied
Using usleep() timing
font: can't open file: /home/q127038/.mplayer/font/font.desc
font: can't open file: /share/caefs1/GNU/RedHat-7.1/usr/local///share/mplayer/font/font.desc
Can't open input config file /home/q127038/.mplayer/input.conf : No such file or directory
Falling back on default (hardcoded) input config

Playing view.mov
Detected QuickTime/MOV file format!
--------------
MOV track #0: 36 chunks, 36 samples
Image size: 1200 x 700 (24 bpp)
Display size: 1200 x 700
Fourcc: rle   Codec: 'Animation'
--------------
vo: X11 running at 1600x1024 with depth 24 and 32 bpp (":0.0" => local display)
==========================================================================
Opening video decoder: [qtrle] Quicktime Animation (RLE) decoder
VDec: vo config request - 1200 x 700 (preferred csp: BGR 24-bit)  
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 1200x700 => 1200x700 BGR 24-bit 
Detected video codec: [qtrle] vfm:14 (Quicktime Animation (RLE))
==========================================================================
Audio: no sound!!!
Start playing...
V:   0.0    1   0%  0%  0.0% 0 0 0%

MPlayer interrupted by signal 11 in module: decode_video 
- MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. For details, see DOCS/bugreports.html section 5.b.
- MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/bugreports.html and follow instructions there. We can't and won't help unless you provide these informations when reporting a possible bug.