I've seen this a lot lately. due to tuning problems with my nova-t 500s, I've gotten frequent zero length recordings. Playing back these either using the xine plugin, or xineliboutput, causes VDR to crash and restart.
I'm using yavdr with only trivial modifications.
On Tue, Mar 13, 2012 at 8:08 AM, Torgeir Veimo torgeir@netenviron.com wrote:
I've seen this a lot lately. due to tuning problems with my nova-t 500s, I've gotten frequent zero length recordings. Playing back these either using the xine plugin, or xineliboutput, causes VDR to crash and restart.
I'm using yavdr with only trivial modifications.
I compile VDR myself and never have this problem. I use vdr-xine and have been test softhddevice but in case of an empty recording, VDR just returns to live tv. Sounds like a yavdr problem -- last I heard yavdr uses a bunch of patches but since I don't use it I don't know that 100%.
last I heard yavdr uses a bunch of patches but since I don't use it I don't know that 100%.
Well that's always good and cheap to talk about things about any individual heard about ... :-(
@Torgeir
Which version of yavdr do you use? Might it be possible to open a case on vdr-portal.de in yavdr sub-forum? English language is pretty much ok, at least I'm able to answer ... ;-)
Regards fnu of yavdr-team
On Tue, Mar 13, 2012 at 11:54 AM, Frank Neumann vdr@auktion.hostingkunde.de wrote:
last I heard yavdr uses a bunch of patches but since I don't use it I don't know that 100%.
Well that's always good and cheap to talk about things about any individual heard about ... :-(
There is nothing wrong with passing along what you've heard. Furthermore, I intentionally pointed out that I don't know that to be 100% true. Your claim that my comment is "cheap" is completely uncalled for. If you wanted to reply, rather than trying to insult me you should have clarified that YES yavdr applies patches to VDR, or NO it does not.
Your claim that my comment is "cheap" is completely uncalled for.
Well, just needless, even you should realize that comments like this don't help anybody.
That's what I read: "Hey stupid I'm super cool and able to compile VDR by myself, you're a nobody just able to use this bullshit yaVDR ..."
And I guess I'm pretty much not alone with this impression, or did you had just a fragment of any helpful value for that guy ...
Cheers fnu
On Tue, Mar 13, 2012 at 12:43 PM, Frank Neumann vdr@auktion.hostingkunde.de wrote:
That's what I read: "Hey stupid I'm super cool and able to compile VDR by myself, you're a nobody just able to use this bullshit yaVDR ..."
Then you're a complete idiot because that is NOT what I said.
Grow up.
Got some hints at the vdr portal on how to get debug output. The crashlog contains this stacktrace;
I presume it would be cause by one of the patches yavdr uses, since it also happens with only the xine plugin enabled. This is yavdr 0.4, with latest updates as of today.
Program terminated with signal 6, Aborted. #0 0x00c06416 in __kernel_vsyscall () #0 0x00c06416 in __kernel_vsyscall () #1 0x0040ae71 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0x0040e34e in abort () from /lib/i386-linux-gnu/libc.so.6 #3 0x004427f7 in ?? () from /lib/i386-linux-gnu/libc.so.6 #4 0x0044cbe1 in ?? () from /lib/i386-linux-gnu/libc.so.6 #5 0x0044e50b in ?? () from /lib/i386-linux-gnu/libc.so.6 #6 0x0045169d in free () from /lib/i386-linux-gnu/libc.so.6 #7 0x001e94d1 in operator delete(void*) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #8 0x080d23c4 in cDvbPlayer::~cDvbPlayer (this=0xaea43030, __in_chrg=<value optimized out>) at dvbplayer.c:323 #9 0x080d24c3 in cDvbPlayer::~cDvbPlayer (this=0xaea43030, __in_chrg=<value optimized out>) at dvbplayer.c:329 #10 0x080d4d7c in cDvbPlayerControl::Stop (this=0xaea42ec0) at dvbplayer.c:963 #11 0x081080dd in cReplayControl::Stop (this=0xaea42ec0) at menu.c:5165 #12 0x08107e2d in cReplayControl::~cReplayControl (this=0xaea42ec0, __in_chrg=<value optimized out>) at menu.c:5131 #13 0x007607f1 in myReplayControl::~myReplayControl() () from /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.22 #14 0x00760842 in myReplayControl::~myReplayControl() () from /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.22 #15 0x081214c0 in cControl::Shutdown () at player.c:106 #16 0x081615fa in main (argc=49, argv=0xbfa68634) at vdr.c:1241
Hi Tor,
well honestly, I don't think it's one of the patches, it seems for me rather to be again somehow "vdr-plugin-extrecmenu".
The VDR version as of today has been tested since 2 month, to become part for stable-vdr (first lucid, then natty) and nobody did realize this problem. But I need to mention, pretty sure nobody did test extrecmenu, it isn't part of "yavdr-essential".
Could you please try to replay these recordings using the VDRs own functionality?
Regards fnu
PS.: It would be much easier to chat about this in a thread in vdr-portal.de, instead of bothering this mailing list.
-----Original Message----- From: vdr-bounces@linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf Of Torgeir Veimo Sent: Wednesday, March 14, 2012 1:34 AM To: VDR Mailing List Subject: Re: [vdr] vdr crashes when replaying zero length recording
Got some hints at the vdr portal on how to get debug output. The crashlog contains this stacktrace;
I presume it would be cause by one of the patches yavdr uses, since it also happens with only the xine plugin enabled. This is yavdr 0.4, with latest updates as of today.
Program terminated with signal 6, Aborted. #0 0x00c06416 in __kernel_vsyscall () #0 0x00c06416 in __kernel_vsyscall () #1 0x0040ae71 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0x0040e34e in abort () from /lib/i386-linux-gnu/libc.so.6 #3 0x004427f7 in ?? () from /lib/i386-linux-gnu/libc.so.6 #4 0x0044cbe1 in ?? () from /lib/i386-linux-gnu/libc.so.6 #5 0x0044e50b in ?? () from /lib/i386-linux-gnu/libc.so.6 #6 0x0045169d in free () from /lib/i386-linux-gnu/libc.so.6 #7 0x001e94d1 in operator delete(void*) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #8 0x080d23c4 in cDvbPlayer::~cDvbPlayer (this=0xaea43030, __in_chrg=<value optimized out>) at dvbplayer.c:323 #9 0x080d24c3 in cDvbPlayer::~cDvbPlayer (this=0xaea43030, __in_chrg=<value optimized out>) at dvbplayer.c:329 #10 0x080d4d7c in cDvbPlayerControl::Stop (this=0xaea42ec0) at dvbplayer.c:963 #11 0x081080dd in cReplayControl::Stop (this=0xaea42ec0) at menu.c:5165 #12 0x08107e2d in cReplayControl::~cReplayControl (this=0xaea42ec0, __in_chrg=<value optimized out>) at menu.c:5131 #13 0x007607f1 in myReplayControl::~myReplayControl() () from /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.22 #14 0x00760842 in myReplayControl::~myReplayControl() () from /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.22 #15 0x081214c0 in cControl::Shutdown () at player.c:106 #16 0x081615fa in main (argc=49, argv=0xbfa68634) at vdr.c:1241
-- -Tor
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 14 March 2012 10:57, Frank Neumann vdr@auktion.hostingkunde.de wrote:
Hi Tor,
well honestly, I don't think it's one of the patches, it seems for me rather to be again somehow "vdr-plugin-extrecmenu".
The VDR version as of today has been tested since 2 month, to become part for stable-vdr (first lucid, then natty) and nobody did realize this problem. But I need to mention, pretty sure nobody did test extrecmenu, it isn't part of "yavdr-essential".
Could you please try to replay these recordings using the VDRs own functionality?
I simply temporarily removed /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.22 (just negging it in oder.conf didn't work) and restarted vdr-dbg. Here's the crashlog from that run;
On 14.03.2012 02:17, Torgeir Veimo wrote:
On 14 March 2012 10:57, Frank Neumannvdr@auktion.hostingkunde.de wrote:
Hi Tor,
well honestly, I don't think it's one of the patches, it seems for me rather to be again somehow "vdr-plugin-extrecmenu".
The VDR version as of today has been tested since 2 month, to become part for stable-vdr (first lucid, then natty) and nobody did realize this problem. But I need to mention, pretty sure nobody did test extrecmenu, it isn't part of "yavdr-essential".
Could you please try to replay these recordings using the VDRs own functionality?
I simply temporarily removed /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.22 (just negging it in oder.conf didn't work) and restarted vdr-dbg. Here's the crashlog from that run; ... Command line: /usr/bin/vdr-dbg --lirc=/var/run/lirc/lircd -v /srv/vdr/video.00 -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr/lib/vdr/vdr-recordingaction -s -E /var/cache/vdr/epg.data -u vdr -g /tmp --port 6419 -w 0 -D 1 2 3 -Pxine -r -Plcdproc -Piptv -Ptext2skin -Pmenuorg -Pfemon -Pepgsearch -f /usr/bin/svdrpsend -Pxvdr -t 10 -Pstreamdev-server -Pchannellists -Pdbus2vdr -Pskinenigmang --logodir=/usr/share/vdr-enigmang-icons --epgimages=/var/cache/vdr/epgimages -Plive --port=8008 --ip=0.0.0.0 --epgimages=/var/cache/vdr/epgimages -Prestfulapi --port=8002 --ip=0.0.0.0 --epgimages=/var/cache/vdr/epgimages --channellogos=/usr/share/vdr-channellogos -Pquickepgsearch -Pskinpearlhd --epgimages=/var/cache/vdr/epgimages -Pmarkad -Pepgsearchonly -Pwirbelscan -Pconflictcheckonly -Pdynamite &> /tmp/vdr.log
Versions:
vdr (1.7.22/1.7.22) - The Video Disk Recorder xine (0.9.4) - Software based playback using xine lcdproc (0.0.10-jw8) - LCDproc output iptv (0.4.2) - Experience the IPTV text2skin (1.3.2+git) - Loader for text-based skins menuorg (0.4.5) - Reorganizes the main menu femon (1.7.11) - DVB Signal Information Monitor (OSD) epgsearch (1.0.1) - search the EPG for repeats and more xvdr (0.9.5) - VDR-Network-Streaming-Interface (XVDR) Server streamdev-server (0.5.1-git) - VDR Streaming Server channellists (0.0.4) - Manage your channellists dbus2vdr (0.0.2j) - expose methods for controlling vdr via DBus skinenigmang (0.1.1) - EnigmaNG skin live (0.2.0) - Live Interactive VDR Environment restfulapi (0.1.0) - Offers a RESTful-API to retrieve data from VDR quickepgsearch (0.0.1) - Quick search for broadcasts skinpearlhd (0.0.1) - PearlHD Skin markad (0.1.3) - Mark advertisements epgsearchonly (0.0.1) - Direct access to epgsearch's search menu wirbelscan (0.0.7) - DVB and pvrinput channel scan for VDR conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu dynamite (0.0.9a) - attach/detach devices on the fly
Please run *plain vanilla* VDR 1.7.26 with only the most essential plugins (which would be the *output* plugin, nothing else) and see if it still crashes. If it does, please make a tar-archive of this empty recording and send it to me for further investigation.
Klaus
-
Frank Neumann -
Klaus Schmidinger -
Torgeir Veimo -
VDR User