[Mplayer-users] another broken one
Juergen Keil
jk at tools.de
Fri Aug 10 20:17:04 CEST 2001
> I've tried to reproduce the "signal 11" problem with the sig11broken.avi
> file you transfered to the incoming directory on the ftp server, but I don't
> think I succeeded. I've tried it on Linux & Solaris. I get a signal 11,
> indeed; but I get that ~14.4 seconds into the video, and that's apparently
> when the truncated (!) avi file ends.
There's some progress now...
It seems the problem is with "-framedrop" vs no framedrop.
I've now seen the following commands crash at 7.4 seconds (the exact position
in the video probably depends on your system's speed) into the video:
./mplayer -v -framedrop -vo x11 sig11broken.avi
./mplayer -v -framedrop -vo sdl:x11 sig11broken.avi
(mplayer does *not* crash if I remove the -framedrop option)
% gdb ./mplayer
...
(gdb) run -v -framedrop -vo x11 sig11broken.avi
...
Initial PTS delay: 0.029 sec ->0.067 (bps: 0.019) audio_delay=0.000
v: audio_delay=0.000 buffer_delay=0.338 a.pts=0.500 v.pts=0.133
A: 7.9 ( 7.9) V: 7.6 A-V: 0.284 ct: 0.088 230 34% 8% 4.3% 0 0
frame drop 1, -0.29
A: 8.0 ( 7.9) V: 7.6 A-V: 0.269 ct: 0.091 231 34% 8% 4.3% 1 0
Program received signal SIGSEGV, Segmentation fault.
0x100116fb in ?? ()
(gdb) x/20i 0x100116c0
0x100116c0: incl (%ecx)
0x100116c2: add %al,(%eax)
0x100116c4: mov %ebx,(%esp,1)
0x100116c7: and $0x1ff,%esi
0x100116cd: mov 0x6e(%esp,1),%cl
0x100116d1: mov 0x1006fd22(%eax,%edi,1),%bh
0x100116d8: mov 0x1006ff8b(%eax,%ebp,1),%bl
0x100116df: add $0xc,%edx
0x100116e2: shl $0x10,%ebx
0x100116e5: mov %edx,0x28(%esp,1)
0x100116e9: mov 0x100701a1(%eax,%esi,1),%bh
0x100116f0: mov 0x6d(%esp,1),%al
0x100116f4: mov 0x1006fd1f(%ecx,%edi,1),%bl
0x100116fb: mov %ebx,0xfffffffc(%edx) <-----
0x100116fe: mov 0x1006ff87(%ecx,%ebp,1),%bh
0x10011705: mov 0x100701a0(%ecx,%esi,1),%bl
0x1001170c: mov 0x6c(%esp,1),%cl
0x10011710: shl $0x10,%ebx
0x10011713: mov 0x1006fd21(%eax,%edi,1),%bh
0x1001171a: mov 0x1006ff8b(%eax,%ebp,1),%bl
(gdb) print $edx
$1 = 12
(gdb) x/wx 0xfffffffc+$edx
0x8: Cannot access memory at address 0x8
It seems that, as soon as MPlayer decides to drop a frame...
v
v
A: 7.9 ( 7.9) V: 7.6 A-V: 0.284 ct: 0.088 230 34% 8% 4.3% 0 0
frame drop 1, -0.29
A: 8.0 ( 7.9) V: 7.6 A-V: 0.269 ct: 0.091 231 34% 8% 4.3% 1 0
^
^
... it crashes inside the win32 DLL.
--
Jürgen Keil jk at tools.de
Tools GmbH +49 (228) 9858011
_______________________________________________
Mplayer-users mailing list
Mplayer-users at lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/mplayer-users
More information about the MPlayer-users
mailing list