Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-31 Thread Jouni Karvo
Jouni Karvo kirjoitti: > > So it seems the syscall numbers have changed at some point. I am afraid > if the libc is now broken due to this. This has not happened to me > before, so I don't actually know what would be the good thing to do. > But forcing the syscall number to 178 does not actually f

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-30 Thread Jouni Karvo
hi, Reinhard Nissl kirjoitti: > Please report the logged error message. > Actually, your patch immediately segfaulted. But I can see some problem: The include files from the distro tell me: k...@vdr:/usr/include$ grep __NR_gettid */* asm/unistd_32.h:#define __NR_gettid224 asm/unistd

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-27 Thread Reinhard Nissl
Hi, Am 27.01.2010 06:26, schrieb Jouni Karvo: > A quick google did not tell me how to enable thread numbers in the log. > Is it a specific library package to be installed or is it some certain > kernel option? Edit VDR's thread.c and replace method cThread::ThreadId() with the below version: t

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-26 Thread Jouni Karvo
hi, Reinhard Nissl kirjoitti: > > This doesn't look like a vdr-xine issue. > > Indeed not. It just occurred to me that even though I had not started other plugins, there was the yaepghd patch included. I removed that, and it seems now the segmentation fault is gone. (for a few minutes at l

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-26 Thread Reinhard Nissl
Hi, Am 26.01.2010 19:18, schrieb Jouni Karvo: > I included logs, please let me know what to try next. Both of your so far posted logs show this scenario: > Jan 26 19:54:55 vdr vdr: [-1] buffer usage: 70% (tid=-1) > Jan 26 19:54:55 vdr vdr: [-1] buffer usage: 80% (tid=-1) > Jan 26 19:54:55 vdr v

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-26 Thread Jouni Karvo
... and here the backtrace without -O2, if it helps more... #0 0x004717be in cHashObject::Object (this=0x41) at tools.h:525 525 cListObject *Object(void) { return object; } (gdb) bt #0 0x004717be in cHashObject::Object (this=0x41) at tools.h:525 #1 0x00470153 in cChannels:

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-26 Thread Jouni Karvo
Jouni Karvo kirjoitti: > Jouni Karvo kirjoitti: > >> hi, >> >> I just turned to 64bit, and it seems vdr dumps core there... >> >> compiled with g++-4.3 >> >> >> > answering to myself. Compiling with g++-4.1 removes the segmentation fault. > But it does not. It does segfault, and in

Re: [vdr] vdr-1.7.11 (+ vdr-xine) segfaults

2010-01-25 Thread Jouni Karvo
Jouni Karvo kirjoitti: > hi, > > I just turned to 64bit, and it seems vdr dumps core there... > > compiled with g++-4.3 > > answering to myself. Compiling with g++-4.1 removes the segmentation fault. I don't know whether this is related, but g++-4.3 warns in many places about expressions with