I am running arch Linux with vdr4arch and live plugin crashes right after I login into it. I wonder if there is patch for it or am I missing configuration settings ? I see
Ich bin mit Arch Linux mit vdr4arch und Live-Plugin abstürzt nachdem ich anmelden hinein. Ich frage mich, ob es für sie oder Patch fehlen mir Konfigurationseinstellungen? Ich sehe
ERROR
--:--
No server response!
==8313== Thread 24:
==8313== Invalid read of size 8
==8313== at 0x47039A: cChannel::Name() const (in /usr/bin/vdr)
==8313== by 0xB874B8A: ??? (in /usr/lib/vdr/plugins/libvdr-live.so.2.1.6)
==8313== by 0xBB8D57B: tnt::Worker::dispatch(tnt::HttpRequest&, tnt::HttpRepl y&) (in /usr/lib/libtntnet.so.12.0.0)
==8313== by 0xBB8E6D1: tnt::Worker::processRequest(tnt::HttpRequest&, std::io stream&, unsigned int) (in /usr/lib/libtntnet.so.12.0.0)
==8313== by 0xBB8F326: tnt::Worker::run() (in /usr/lib/libtntnet.so.12.0.0)
==8313== by 0xBB8FCF9: cxxtools::DetachedThread::exec() (in /usr/lib/libtntne t.so.12.0.0)
==8313== by 0xBE8B3DE: ??? (in /usr/lib/libcxxtools.so.9.0.0)
==8313== by 0x508F123: start_thread (in /usr/lib/libpthread-2.19.so)
==8313== by 0x68C64BC: clone (in /usr/lib/libc-2.19.so)
==8313== Address 0x18 is not stack'd, malloc'd or (recently) free'd
==8313==
==8313==
==8313== Process terminating with default action of signal 11 (SIGSEGV)
==8313== Access not within mapped region at address 0x18
==8313== at 0x47039A: cChannel::Name() const (in /usr/bin/vdr)
==8313== by 0xB874B8A: ??? (in /usr/lib/vdr/plugins/libvdr-live.so.2.1.6)
==8313== by 0xBB8D57B: tnt::Worker::dispatch(tnt::HttpRequest&, tnt::HttpRepl y&) (in /usr/lib/libtntnet.so.12.0.0)
==8313== by 0xBB8E6D1: tnt::Worker::processRequest(tnt::HttpRequest&, std::io stream&, unsigned int) (in /usr/lib/libtntnet.so.12.0.0)
==8313== by 0xBB8F326: tnt::Worker::run() (in /usr/lib/libtntnet.so.12.0.0)
==8313== by 0xBB8FCF9: cxxtools::DetachedThread::exec() (in /usr/lib/libtntne t.so.12.0.0)
==8313== by 0xBE8B3DE: ??? (in /usr/lib/libcxxtools.so.9.0.0)
==8313== by 0x508F123: start_thread (in /usr/lib/libpthread-2.19.so)
==8313== by 0x68C64BC: clone (in /usr/lib/libc-2.19.so)
==8313== If you believe this happened as a result of a stack
==8313== overflow in your program's main thread (unlikely but
==8313== possible), you can try to increase the size of the
==8313== main thread stack using the --main-stacksize= flag.
==8313== The main thread stack size used in this run was 8388608.
==8313==
==8313== HEAP SUMMARY:
==8313== in use at exit: 85,289,645 bytes in 559,645 blocks
==8313== total heap usage: 972,064 allocs, 412,419 frees, 147,904,818 bytes al located
==8313==
==8313== LEAK SUMMARY:
==8313== definitely lost: 8,328 bytes in 12 blocks
==8313== indirectly lost: 614 bytes in 19 blocks
==8313== possibly lost: 4,310,743 bytes in 727 blocks
==8313== still reachable: 80,969,960 bytes in 558,887 blocks
==8313== suppressed: 0 bytes in 0 blocks
==8313== Rerun with --leak-check=full to see details of leaked memory
==8313==
==8313== For counts of detected and suppressed errors, rerun with: -v
==8313== Use --track-origins=yes to see where uninitialised values come from
==8313== ERROR SUMMARY: 737 errors from 94 contexts (suppressed: 1 from 1)