[vdr] Re: Coredump - vdr 1.3.9 at eit.c:205

[Wolfgang Fritz <wolfgang.fritz@gmx.net>]

Wolfgang Fritz wrote:
> Stefan Hagendorn wrote:
> 
>>Hi,
>>
>>since this evening my vdr starts to coredump over and over - I've no Idea 
>>what this can cause and I'm not a programmer. Some nice ppl in #LinuxDVB 
>>on Efnet toldme how to handle a core file and how to analyze it and do a 
>>backtrace by gdb. Maybe anone got a clue what this could be - maybe 
>>malformed EPG infos again ... ?! 
>>
> 
> 
> Me too...
> 
> I can not see the the "segmentation fault" message (no monitor connected
> to the vdr box) and can not find a core file (have to check the ulimit
> settings). No messages in /var/log/messages related to a crash.
> 

Just to confirm: I get the same crash (got a core dump after setting
proper ulimits).

Wolfgang

> This seems to happen with certain programs only (maybe on the same
> transponder, have to check this too). Affected programs ZDF, 3sat, ZDF info)
> 
> Switched back to 1.2.6 which is working fine.
> 
> Wolfgang
> 
> 
>>Thanks
>>Stefan
>>
>>[root@voyager VDR]# ./vdr -Premote
>>Segmentation fault (core dumped)
>>[root@voyager VDR]# gdb vd
>>vdr                              vdr.1                            vdr.c
>>vdr-1.3.7-AC3OverDVB-0.2.5.diff  vdr.5                            vdr.o
>>[root@voyager VDR]# gdb vdr co
>>config.c   config.h   config.o   core.3104
>>[root@voyager VDR]# gdb vdr core.3104
>>GNU gdb 6.0-2mdk (Mandrake Linux)
>>Copyright 2003 Free Software Foundation, Inc.
>>GDB is free software, covered by the GNU General Public License, and you 
>>are
>>welcome to change it and/or distribute copies of it under certain 
>>conditions.
>>Type "show copying" to see the conditions.
>>There is absolutely no warranty for GDB.  Type "show warranty" for 
>>details.
>>This GDB was configured as "i586-mandrake-linux-gnu"...Using host 
>>libthread_db library "/lib/tls/libthread_db.so.1".
>>
>>Core was generated by `./vdr -Premote'.
>>Program terminated with signal 11, Segmentation fault.
>>
>>warning: current_sos: Can't read pathname for load map: Input/output error
>>
>>Reading symbols from /usr/lib/libjpeg.so.62...done.
>>Loaded symbols for /usr/lib/libjpeg.so.62
>>Reading symbols from /lib/tls/libpthread.so.0...done.
>>Loaded symbols for /lib/tls/libpthread.so.0
>>Reading symbols from /lib/libdl.so.2...done.
>>Loaded symbols for /lib/libdl.so.2
>>Reading symbols from /usr/lib/libstdc++.so.5...done.
>>Loaded symbols for /usr/lib/libstdc++.so.5
>>Reading symbols from /lib/tls/libm.so.6...done.
>>Loaded symbols for /lib/tls/libm.so.6
>>Reading symbols from /lib/libgcc_s.so.1...done.
>>Loaded symbols for /lib/libgcc_s.so.1
>>Reading symbols from /lib/tls/libc.so.6...done.
>>Loaded symbols for /lib/tls/libc.so.6
>>Reading symbols from /lib/ld-linux.so.2...done.
>>Loaded symbols for /lib/ld-linux.so.2
>>Reading symbols from ./PLUGINS/lib/libvdr-remote.so.1.3.9...done.
>>Loaded symbols for ./PLUGINS/lib/libvdr-remote.so.1.3.9
>>Reading symbols from /usr/lib/gconv/ISO8859-15.so...done.
>>Loaded symbols for /usr/lib/gconv/ISO8859-15.so
>>#0  0x080978a7 in cEIT (this=0x422cf950, Schedules=0x817d0e0, 
>>Source=35008, Tid=80 'P', Data=0x422cfa50 "Pÿ\036mhÝip\0047")
>>    at eit.c:205
>>205           delete ShortEventDescriptor;
>>(gdb) bt
>>#0  0x080978a7 in cEIT (this=0x422cf950, Schedules=0x817d0e0, 
>>Source=35008, Tid=80 'P', Data=0x422cfa50 "Pÿ\036mhÝip\0047")
>>    at eit.c:205
>>#1  0x0809816c in cEitFilter::Process(unsigned short, unsigned char, 
>>unsigned char const*, int) (this=0x8b936b0, Pid=18,
>>    Tid=80 'P', Data=0x422cfa50 "Pÿ\036mhÝip\0047", Length=3873) at 
>>eit.c:270
>>#2  0x080c4647 in cSectionHandler::Action() (this=0x8b93320) at 
>>sections.c:199
>>#3  0x080d49f8 in cThread::StartThread(cThread*) (Thread=0x8b93320) at 
>>thread.c:189
>>#4  0x4004a7d3 in start_thread () from /lib/tls/libpthread.so.0
>>#5  0x4022fb4a in clone () from /lib/tls/libc.so.6
>>Current language:  auto; currently c++
>>(gdb)
>>
>>
> 
> 
> 
> 
>