[vdr] Some backtraces of my segfaulting vdr-1.2.6

Rainer Zocholl UseNet-Posting-Nospam-74308- at zocki.toppoint.de
Fri Jun 24 16:44:00 CEST 2005

sockpuppet at hanno.de(Hanno Mueller)  24.06.05 13:38

>>>I'm using the c't vdr binary packages from e-tobi.net. I'll see if I
>>>can compile my own from their sources.
>> Maybe help your this german tutorial,
>> how build vdr from debian source package :
>> http://www.e-tobi.net/blog/=2004-09-21_compiling

>I followed his guidelines, but the resulting binary appears to use
>different default values than the one he distributes in his .deb
>It was quite difficult to get it working with the c't vdr
>start scripts, 

Hm, as "c't vdr" is based on GPL software all required
files must be available, including "Makefiles".

>in the end I had to use --allow-root, thenit appeared
>to use the same or at least similar setting.

It's true that you can't just say "make" and get running
binary for you box.
But most switches are documented and obvious.

>My debugging binary segfaults, as well. 

That's good!

>I have collected several coredumps and these are the backtraces from them. 
>If you need one particular coredump, let me know.

I assume that the DVB developers will be of more help.

>As far as I can tell, there must be faulty EPG data.

Why do you assume that?

>Where do I go from here? 
>How can I find out which channel is sending the broken data? 

Every(!) external MUST be considered beeing broken!
Else the software is broken.

>And is there a possibility that the EPG data is
>broken because my card (or its driver) is broken?

Because most drivers needs "reverse enigneering" t's very likely, that
the driver is not perfect.

You have switched OFF NTPL etc.?
Rainer---<=====>                         Vertraulich
         <=====>--------------ocholl, Kiel, Germany ------------

More information about the vdr mailing list