[vdr] Re: segmentation fault immediately after start of vdr

[Rene Bartsch <ml@bartschnet.de>]

Am Mit, 2003-06-25 um 16.18 schrieb gfiala@s.netic.de:

> 
> I have similar (strange) oops'es but thought it would be because i
> have no
> signal connected to my DVB-s, there is another thread about this in
> linux-dvb.
> (i have exactly the same driver version running) but the problems
> appear after
> some time of operation and affect other programs as well. As one would
> expect
> seeing what kernel-module is suppposed to produce the null-pointer
> dereferenze,
> but which module it actually is seems to be random. But without DVB
> the problem
> is gone so it has to be something with that driver.
> 

I'm using the 1.0.0pre4 mdk-driver package from Guido Draheim and have
similar problems.

My setup is vanilla VDR 1.2.0 with streamdev-plugin 0.1.0beta3 and
DEBUG_OSD=1. When I have used dvb-femon before VDR it doesn't work (only
blank screen on terminal, no reaction on keys. When using dvb-femon
while VDR is running, more and more artefarcts appear until
streamdev-plugin stops streaming, although VDR is still running.
This also happens when I stop dvb-femon after a short time of use.

Walter should check if it also appears when he doesn't use additional
progs accessing dvb/video-devices.

Rene



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.