Hallo,
habe mal wieder etwas, was ein Linuxprofi vllt. besser versteht.
Hatte gestern Abend mal den lts-wily installiert.
Seitdem habe ich beim Beenden des VDR immer folgenden segfault
Code
Feb 24 09:04:07 VDR kernel: [ 6838.712627] Socket Handler[3336]: segfault at 7fd38aa8324d ip 00007fd38aa8324d sp 00007fd3497f98b0 error 14 in libpcre.so.3.13.1[7fd38ac8c000+3d000]
Es wird auch ein core geschrieben, welcher aber sehr schweigsam daher kommt.
Code
root@VDR:/var/log/vdr# gdb vdr core.3290
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from vdr...Reading symbols from /usr/lib/debug/.build-id/78/7f6a3da5524be89677f8729b261407b9257b44.debug...done.
done.
[New LWP 3336]
[New LWP 3290]
[New LWP 3351]
[New LWP 4552]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/vdr'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fd38aa8324d in ?? ()
(gdb) bt full
#0 0x00007fd38aa8324d in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)
Alles anzeigen
Hat dazu jemand eine Idee?
Beeinträchtigungen im VDR-Betrieb habe ich dadurch keine.
Gruss.
Markus