Hi,
Anyone using autosort? I recently updated autosort 0.0.10 to 0.1.3 because 0.0.10 could not handle large sorting jobs without getting interrupted by some kind of watchdog/timeout and vdr restart (even with -w 0). With 0.1.3 I get this about once per hour.
Core was generated by `vdr -c/etc/vdr -E/etc/vdr -v/opt/vdr -L/usr/local/lib/vdr -Pxineliboutput --loc'. Program terminated with signal 11, Segmentation fault. #0 0xb7c2036a in free () from /lib/i686/cmov/libc.so.6 (gdb) where #0 0xb7c2036a in free () from /lib/i686/cmov/libc.so.6 #1 0xb74fceb1 in cMenuTimeStamps (this=0xb22f72dc) at autosort_menu.c:217 #2 0xb74fae5d in cAutoSortMainThread::LoopChannels (this=0x8aee1e0) at autosort_main_thread.c:274 #3 0xb74fb08a in cAutoSortMainThread::Action (this=0x8aee1e0) at autosort_main_thread.c:61 #4 0x0811ad8c in cThread::StartThread (Thread=0x8aee1e0) at thread.c:255 #5 0xb7ecd4fb in start_thread () from /lib/i686/cmov/libpthread.so.0 #6 0xb7c8793e in clone () from /lib/i686/cmov/libc.so.6
I found a patch from Debian for the configuration directory problem. Are there patches for this?
BR, Seppo
Seppo Ingalsuo wrote:
#0 0xb7c2036a in free () from /lib/i686/cmov/libc.so.6 #1 0xb74fceb1 in cMenuTimeStamps (this=0xb22f72dc) at autosort_menu.c:217
I wonder if commenting out free() from that function is the right solution? At least timestamp menu from autosort plugin setup doesn't crash any more ...
Try implementing a zap() function, checking to see if the pointer doesn't contain a NULL before trying to free data.
On 24/03/2008, Seppo Ingalsuo seppo.ingalsuo@iki.fi wrote:
Seppo Ingalsuo wrote:
#0 0xb7c2036a in free () from /lib/i686/cmov/libc.so.6 #1 0xb74fceb1 in cMenuTimeStamps (this=0xb22f72dc) at autosort_menu.c:217
I wonder if commenting out free() from that function is the right solution? At least timestamp menu from autosort plugin setup doesn't crash any more ...
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-
Seppo Ingalsuo -
Theunis Potgieter