live plugin crashes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Is there a patch for vdr-live as it crashes on accessing website.
==15881== Thread 29:
==15881== Syscall param epoll_ctl(event) points to uninitialised byte(s)
==15881==    at 0x68C6A6A: epoll_ctl (in /usr/lib/libc-2.19.so)
==15881==    by 0xBB78452: tnt::PollerImpl::addFd(int) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB78933: tnt::PollerImpl::append_new_jobs() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB78B81: tnt::PollerImpl::run() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBE8A3DE: ??? (in /usr/lib/libcxxtools.so.9.0.0)
==15881==    by 0x508F123: start_thread (in /usr/lib/libpthread-2.19.so)
==15881==    by 0x68C64BC: clone (in /usr/lib/libc-2.19.so)
==15881==  Address 0x213accc8 is on thread 29's stack
==15881==
==15881== Thread 24:
==15881== Source and destination overlap in memcpy(0x1eba4c48, 0x1eba4c60, 48)
==15881==    at 0x4C2CC93: memcpy@@GLIBC_2.14 (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==15881==    by 0xBB73529: tnt::Messageheader::removeHeader(char const*) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB737F4: tnt::Messageheader::setHeader(char const*, char const*, bool) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xB888E6A: ??? (in /usr/lib/vdr/plugins/libvdr-live.so.2.1.6)
==15881==    by 0xBB8C57B: tnt::Worker::dispatch(tnt::HttpRequest&, tnt::HttpReply&) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8D6D1: tnt::Worker::processRequest(tnt::HttpRequest&, std::iostream&, unsigned int) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8E326: tnt::Worker::run() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8ECF9: cxxtools::DetachedThread::exec() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBE8A3DE: ??? (in /usr/lib/libcxxtools.so.9.0.0)
==15881==    by 0x508F123: start_thread (in /usr/lib/libpthread-2.19.so)
==15881==    by 0x68C64BC: clone (in /usr/lib/libc-2.19.so)
==15881==
Jun  7 09:04:36.087 [core.pids] 0/0: now tuned to source 5300faf6(S129.0W) transponder 33e98
Jun  7 09:04:36.089 [core.pids] 1/0: now tuned to source 5300faf6(S129.0W) transponder 33eb5
==15881== Thread 33:
==15881== Invalid read of size 8
==15881==    at 0x47039A: cChannel::Name() const (in /usr/bin/vdr)
==15881==    by 0xB8737EA: ??? (in /usr/lib/vdr/plugins/libvdr-live.so.2.1.6)
==15881==    by 0xBB8C57B: tnt::Worker::dispatch(tnt::HttpRequest&, tnt::HttpReply&) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8D6D1: tnt::Worker::processRequest(tnt::HttpRequest&, std::iostream&, unsigned int) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8E326: tnt::Worker::run() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8ECF9: cxxtools::DetachedThread::exec() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBE8A3DE: ??? (in /usr/lib/libcxxtools.so.9.0.0)
==15881==    by 0x508F123: start_thread (in /usr/lib/libpthread-2.19.so)
==15881==    by 0x68C64BC: clone (in /usr/lib/libc-2.19.so)
==15881==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
==15881==
==15881==
==15881== Process terminating with default action of signal 11 (SIGSEGV)
==15881==  Access not within mapped region at address 0x18
==15881==    at 0x47039A: cChannel::Name() const (in /usr/bin/vdr)
==15881==    by 0xB8737EA: ??? (in /usr/lib/vdr/plugins/libvdr-live.so.2.1.6)
==15881==    by 0xBB8C57B: tnt::Worker::dispatch(tnt::HttpRequest&, tnt::HttpReply&) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8D6D1: tnt::Worker::processRequest(tnt::HttpRequest&, std::iostream&, unsigned int) (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8E326: tnt::Worker::run() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBB8ECF9: cxxtools::DetachedThread::exec() (in /usr/lib/libtntnet.so.12.0.0)
==15881==    by 0xBE8A3DE: ??? (in /usr/lib/libcxxtools.so.9.0.0)
==15881==    by 0x508F123: start_thread (in /usr/lib/libpthread-2.19.so)
==15881==    by 0x68C64BC: clone (in /usr/lib/libc-2.19.so)
==15881==  If you believe this happened as a result of a stack
==15881==  overflow in your program's main thread (unlikely but
==15881==  possible), you can try to increase the size of the
==15881==  main thread stack using the --main-stacksize= flag.
==15881==  The main thread stack size used in this run was 8388608.
==15881==
==15881== HEAP SUMMARY:
==15881==     in use at exit: 69,959,814 bytes in 397,507 blocks
==15881==   total heap usage: 846,366 allocs, 448,859 frees, 120,924,498 bytes allocated
==15881==
==15881== LEAK SUMMARY:
==15881==    definitely lost: 10,855 bytes in 145 blocks
==15881==    indirectly lost: 507 bytes in 18 blocks
==15881==      possibly lost: 2,207,336 bytes in 705 blocks
==15881==    still reachable: 67,741,116 bytes in 396,639 blocks
==15881==         suppressed: 0 bytes in 0 blocks
==15881== Rerun with --leak-check=full to see details of leaked memory
==15881==
==15881== For counts of detected and suppressed errors, rerun with: -v
==15881== Use --track-origins=yes to see where uninitialised values come from
==15881== ERROR SUMMARY: 733 errors from 95 contexts (suppressed: 1 from 1)
Killed
[root@clio vdr-live]#
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux