[MPlayer-dev-eng] dxr3 output plugin broke with last CVS update

[David Holm]

Hi,
This is probably related to the now famouse lockup problem, I will look 
into this and send a patch asap.
Thanks for pointing it out

//David Holm

Joe Barnett wrote:

>Hello there!
>
>i just updated mplayer CVS last night/today, and dxr3 output plugin
>stopped working (i'm also running latest CVS em8300 stuff).  Note that
>other output plugins work fine, and i get the same behavior regardless
>of the audio output plugin i use.
>
>if I mplayer -vo dxr3 -ao null -vc mpegpes /path/to/mpeg/file.mpeg,
>everything appears to go fine unitl the following line:
>
>V:   0.4    2   0%  0%  0.0% 0 0 0%
>
>note that the numbers here do NOT change, and this is the first
>occurence of the V:xxxxxxxxxxxxxxx line in the terminal.
>
>if i load mplayer in gdb and hit CTRL-C to get a backtrace, i get the
>following output: 
>
>Program received signal SIGINT, Interrupt.
>[Switching to Thread 1024 (LWP 31970)]
>0x406e2b24 in write () from /lib/libc.so.6
>(gdb) bt
>#0  0x406e2b24 in write () from /lib/libc.so.6
>#1  0x401d84bc in __DTOR_END__ () from /lib/libpthread.so.0
>#2  0x4013fbbe in dxr3_subpic_write (buf=0x829c958 "", n=4) at
>dxr3-api.c:108
>#3  0x080ee943 in make_directcolor_cmap ()
>Cannot access memory at address 0xf
>
>
>_______________________________________________
>MPlayer-dev-eng mailing list
>MPlayer-dev-eng at mplayerhq.hu
>http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
>