[MPlayer-dev-eng] memory corruption with new input?

[Felix Buenemann]

Hi,

I think there are some bugs with memory allocation in new input code, when 
running mplayer through gdb I noticed that eg. subtitles weren't displayed 
and a-v was out of sync because the ct-variable was corrupted (showed nan in 
printf line), as soon as I compiled with --disable-new-input it worked 
correctly again.

Also I got mplayer crashed when doing various very fast keypresses (seek, 
switch win/fullscreen/double).
Here are two sample not too usefull gdb backtraces:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 7460)]
0x4052993f in free () from /lib/libc.so.6
(gdb) bt
#0  0x4052993f in free () from /lib/libc.so.6
#1  0x081341aa in mp_cmd_free (cmd=0x835ab60) at input.c:783
#2  0x08053774 in main (argc=4, argv=0xbffff774, envp=0xbffff788) at 
mplayer.c:2570
#3  0x404d27ee in __libc_start_main () from /lib/libc.so.6

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 7475)]
0x4052993f in free () from /lib/libc.so.6
(gdb) bt
#0  0x4052993f in free () from /lib/libc.so.6
#1  0x081341aa in mp_cmd_free (cmd=0x8375870) at input.c:783
#2  0x08053774 in main (argc=6, argv=0xbffff754, envp=0xbffff770) at 
mplayer.c:2570
#3  0x404d27ee in __libc_start_main () from /lib/libc.so.6

-- 
Best Regards,
	Atmos
____________________________________________
- MPlayer Developer - http://mplayerhq.hu/ -
____________________________________________