Re: [vdr] EIT related crash with 2.0.6
On Wed, Apr 16, 2014 at 4:37 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Yes, epgsearch 1.0.1beta5 and epgfixer 0.3.1. FWIW, none of the patches I have touch eit*.[hc] or epg.[hc]. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 17.04.2014 09:04, Ville Skyttä wrote: On Wed, Apr 16, 2014 at 4:37 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Yes, epgsearch 1.0.1beta5 and epgfixer 0.3.1. FWIW, none of the patches I have touch eit*.[hc] or epg.[hc]. Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 17.04.2014 09:04, Ville Skyttä wrote: On Wed, Apr 16, 2014 at 4:37 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Yes, epgsearch 1.0.1beta5 and epgfixer 0.3.1. FWIW, none of the patches I have touch eit*.[hc] or epg.[hc]. Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 04/17/2014 01:01 PM, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. I will go through the source of epgfixer thoroughly to see if any unlocked access to schedules can be found. -- Matti ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 04/17/2014 08:06 PM, Matti Lehtimäki wrote: On 04/17/2014 01:01 PM, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. I will go through the source of epgfixer thoroughly to see if any unlocked access to schedules can be found. I could not find any unlocked use of schedules in epgfixer, so it should not be the cause of problems. There is actually only one situation where schedules are modified and that happens only if epg data is cloned. -- Matti ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On Thu, Apr 17, 2014 at 9:58 PM, Matti Lehtimäki matti.lehtim...@gmail.com wrote: On 04/17/2014 08:06 PM, Matti Lehtimäki wrote: On 04/17/2014 01:01 PM, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. I will go through the source of epgfixer thoroughly to see if any unlocked access to schedules can be found. I could not find any unlocked use of schedules in epgfixer, so it should not be the cause of problems. There is actually only one situation where schedules are modified and that happens only if epg data is cloned. Thanks, I found out that running without epgfixer for a long time wasn't really an option. In the meantime, the third plugin I have that deals with EPG is live which I haven't really used. Will try without it but I'm already certain that if live is to blame, it's not something related to its interactive use but some background task if it has any. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] EIT related crash with 2.0.6
Hello,
I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no
idea if there's a way to trigger it on demand somehow nor do I know
when exactly it happens; I just sometimes find a core file for it. gdb
backtrace attached, my VDR is quite a patched one (the one from
Fedora) but the line numbers appear to make sense for vanilla 2.0.6
too.
Core was generated by `/usr/sbin/vdr --no-kbd --log=1 --vfat --watchdog=60
--shutdown=vdr-shutdown.sh'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 cHashBase::Get (this=0x7fc164be37f8, Id=1397749140) at tools.c:2113
2113 if (hob-id == Id)
(gdb) bt full
#0 cHashBase::Get (this=0x7fc164be37f8, Id=1397749140) at tools.c:2113
hob = 0x78b028c35a680cc3
list = 0x7fc164bf4b40
#1 0x7fc18330baa6 in cEIT::cEIT (this=0x7fc15f7fcd30, Schedules=optimized
out, Source=optimized out, Tid=optimized out,
Data=optimized out, OnlyRunningStatus=optimized out) at eit.c:74
StartTime = optimized out
rEvent = 0x0
d = optimized out
ExtendedEventDescriptors = optimized out
ShortEventDescriptor = optimized out
LanguagePreferenceExt = 25
UseExtendedEventDescriptor = optimized out
LinkChannels = optimized out
Components = optimized out
Duration = 480
newEvent = 0x0
pEvent = optimized out
LanguagePreferenceShort = 25
it = {i = 358}
SegmentStart = 1397746800
SegmentEnd = 1397749620
tm_r = {tm_sec = 42, tm_min = 7, tm_hour = 17, tm_mday = 14, tm_mon =
3, tm_year = 114, tm_wday = 1, tm_yday = 103,
tm_isdst = 1, tm_gmtoff = 10800, tm_zone = 0x7fc183c505a0 EEST}
t = {tm_sec = 42, tm_min = 7, tm_hour = 17, tm_mday = 14, tm_mon = 3,
tm_year = 114, tm_wday = 1, tm_yday = 103,
tm_isdst = 1, tm_gmtoff = 10800, tm_zone = 0x7fc183c505a0 EEST}
channelID = {source = 1124073472, nid = 42249, tid = 12, sid = 64100,
rid = 0, static InvalidID = {source = 0, nid = 0,
tid = 0, sid = 0, rid = 0, static InvalidID = same as static
member of an already seen type}}
handledExternally = optimized out
Empty = false
Modified = false
Now = 1397484462
channel = optimized out
pSchedule = optimized out
SiEitEvent = incomplete type
#2 0x7fc18330d364 in cEitFilter::Process (this=optimized out,
Pid=optimized out, Tid=optimized out,
Data=0x7fc15f7fce60 `\362\357\372d\357\350, incomplete sequence \370,
Length=optimized out) at eit.c:392
EIT = {SI::EIT = {SI::NumberedSection = {SI::CRCSection =
{SI::Section = {SI::Object = {SI::Parsable = {
_vptr.Parsable = 0x7fc1835ea5f0 vtable for cEIT+16,
parsed = true}, data = {data_ = 0x7fc16404f550,
off = 0}}, No data fields}, No data fields}, No data
fields},
eventLoop = {SI::Loop = {SI::VariableLengthPart = {SI::Object
= {SI::Parsable = {
_vptr.Parsable = 0x7fc1835ea5b0 vtable for
SI::StructureLoopSI::EIT::Event+16, parsed = false}, data = {
data_ = 0x7fc16404f550, off = 14}}, length = 736}, No
data fields}, No data fields},
s = 0x7fc15f7fce60}, No data fields}
SchedulesLock = {locked = true}
Schedules = 0x7fc1835f6870 cSchedules::schedules
#3 0x7fc183359f2c in cSectionHandler::Action (this=0x7fc183d13ae0) at
sections.c:211
fi = 0x7fc183d47c00
pid = 18
tid = 96
len = optimized out
buf =
`\362\357\372d\357\350\370\000\f\245\t\350a\327Uݼ\025\000\000\000$\000\000fM1fin\026\005Fanipoju
SumSum (7)\026\005Fanipoju SumSum (7)M1swe\026\vFanipoju SumSum
(7)\026\vFanipoju SumSum
(7)\327Vݼ\025$\000\000\025\000\000bM/fin\025\005Vihannesveijarit
(S)\025\005Vihannesveijarit (S)M/swe\025\vVihann...
r = 754
fh = optimized out
ThreadLock = {thread = 0x7fc183d13ae0, locked = true}
i = optimized out
DeviceHasLock = true
NumFilters = optimized out
pfd = 0x7fc15f7fcdd0
oldStatusCount = 37
#4 0x7fc18337c63f in cThread::StartThread (Thread=0x7fc183d13ae0) at
thread.c:262
No locals.
#5 0x7fc182bcbf33 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#6 0x7fc1815e3ded in clone () from /lib64/libc.so.6
No symbol table info available.
(gdb) quit
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
