VDR EEPG Plugin

From the gdb output it seems that vdr is crashing when returning the source in filter.c, however I can not reproduce the problem, I have tested both master and experimental branch on VDR 1.7.19. Can you provide your vdr version.

dimeptr wrote:

From the gdb output it seems that vdr is crashing when returning the source in filter.c, however I can not reproduce the problem, I have tested both master and experimental branch on VDR 1.7.19. Can you provide your vdr version.

I had vdr 1.7.18 running at the time the crash occured. I was not able to reproduce the crash after this particular day. All seems fine now even with vdr 1.7.20.

The problem occured again yesterday. It looks the same as before.
VDR crashed after running for a few minutes, or shortly after switching to the Sky Select channel.
I recorded the entire transponder for 2 minutes. The resulting file is 541MB. Do you have a place to put it?

I am running latest eepg with vdr-1.7.20 now.

Here is the gdb output from yesterday:

#0 cFilter::Source (this=0xa007f81ebb93010) at filter.c:91
91 return sectionHandler ? sectionHandler->Source() : 0;
(gdb) up
#1 0x00007f81f05c0f40 in cFilterEEPG::Process (this=0x43cdc223, Pid=<value optimized out>, Tid=<value optimized out>,
Data=0x43cdc1e0 "Orderline D:0180-5530000 A:01-49168800 (Preis s. Programm-Magazin)", Length=<value optimized out>)
at eepg.c:3657
3657 tChannelID channelID (Source (), nid, tid, sid);
Current language: auto; currently c++
(gdb) up
#2 0x00000000004c9e91 in cSectionHandler::Action (this=0x7f81e403ab50) at sections.c:212
212 fi->Process(pid, tid, buf, len);
(gdb) up
#3 0x00000000004e3695 in cThread::StartThread (Thread=0x7f81e403ab50) at thread.c:257
257 Thread->Action();
(gdb) up
#4 0x00007f81f9d12fc7 in start_thread () from /lib/libpthread.so.0
(gdb) up
#5 0x00007f81f880964d in clone () from /lib/libc.so.6
(gdb) up
#6 0x0000000000000000 in ?? ()
(gdb) up
Initial frame selected; you cannot go up.

can you enable core dumps on your system and do a stack trace, the log does not help much.

the core dump is enabled with:
ulimit -c unlimited

prior to starting vdr, on the same shell.
after vdr crashes, it will genrate core file on which you can do backtrace with a command similar to this:
gdb path/to/vdr path/to/core

and inside
bt

if you provide this backtrace it will be very helpfull

Hi,
since reporting the bug I disabled eepg to see, if that makes any difference and indeed it did, no such crashes without eepg! I'll now re-enable eepg and then provide a core dump as you ordered.