No difference. However, I get this:
It does not crash without the --threadprofiler. Will now run it with GDB.
Not sure if this should be working and is the real problem. But anyways:
Code:
# ./pilight-daemon -D --threadprofiler
[Mar 15 16:32:11:658242] pilight-daemon: INFO: version 6.0, commit d8f1f7f
[Mar 15 16:32:11:764894] pilight-daemon: ERROR: ----- Thread Profiling -----
[Mar 15 16:32:11:767800] pilight-daemon: ERROR: - thread lirc: 0.000000%
[Mar 15 16:32:11:768171] pilight-daemon: ERROR: - thread socket: 0.000000%
[Mar 15 16:32:11:768467] pilight-daemon: ERROR: - thread ssdp: 0.000000%
[Mar 15 16:32:11:768663] pilight-daemon: ERROR: - thread sender: 0.000000%
[Mar 15 16:32:11:768804] pilight-daemon: ERROR: - thread broadcaster: 0.000000%
[Mar 15 16:32:11:769010] pilight-daemon: ERROR: - thread 433nano: 0.000000%
[Mar 15 16:32:11:769147] pilight-daemon: ERROR: - thread receive parser: 0.000000%
[Mar 15 16:32:11:769336] pilight-daemon: ERROR: - thread events client: 0.000000%
[Mar 15 16:32:11:769481] pilight-daemon: ERROR: - thread events loop: 0.000000%
433MHz Init-- STACKTRACE (10 FRAMES) --
__restore_rt ip = 0x7f157d4f89f0, sp = 0x7fffc88ea440
pthread_getcpuclockid ip = 0x7f157d4f64e0, sp = 0x7fffc88ea8f8
getThreadCPUUsage ip = 0x7f157dc297bf, sp = 0x7fffc88ea900
threads_cpu_usage ip = 0x7f157dc31851, sp = 0x7fffc88ea930
433MHz Receivingpilight_stats ip = 0x40ac60, sp = 0x7fffc88ea960
main ip = 0x40b197, sp = 0x7fffc88ea9d0
__libc_start_main ip = 0x7f157cafbbe5, sp = 0x7fffc88eaa00
_start ip = 0x404039, sp = 0x7fffc88eaac0
ip = (nil), sp = 0x7fffc88eaac8
segmentation faultIt does not crash without the --threadprofiler. Will now run it with GDB.
Not sure if this should be working and is the real problem. But anyways:
Code:
(gdb) run -D --threadprofiler
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/gerwin/Temp/pilight/pilight-daemon -D --threadprofiler
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Mar 15 16:37:14:964654] pilight-daemon: INFO: version 6.0, commit d8f1f7f
[New Thread 0x7ffff679e700 (LWP 21193)]
[New Thread 0x7ffff5f9d700 (LWP 21194)]
[New Thread 0x7ffff579c700 (LWP 21195)]
[New Thread 0x7ffff4f9b700 (LWP 21196)]
[New Thread 0x7fffe7fff700 (LWP 21197)]
[New Thread 0x7fffe77fe700 (LWP 21198)]
[New Thread 0x7fffe6ffd700 (LWP 21199)]
[ Mar 15 16:37:15:85425] pilight-daemon: ERROR: ----- Thread Profiling -----
[ Mar 15 16:37:15:85503] pilight-daemon: ERROR: - thread lirc: 0.000000%
[ Mar 15 16:37:15:85542] pilight-daemon: ERROR: - thread socket: 0.000000%
[ Mar 15 16:37:15:85563] pilight-daemon: ERROR: - thread ssdp: 0.000000%
[ Mar 15 16:37:15:85583] pilight-daemon: ERROR: - thread sender: 0.000000%
[ Mar 15 16:37:15:85600] pilight-daemon: ERROR: - thread broadcaster: 0.000000%
Program received signal SIGSEGV, Segmentation fault.
pthread_getcpuclockid (threadid=0, clockid=0x7fffffffe11c) at ../nptl/sysdeps/unix/sysv/linux/pthread_getcpuclockid.c:35
35 if (INVALID_TD_P (pd))
(gdb) backtrace
#0 pthread_getcpuclockid (threadid=0, clockid=0x7fffffffe11c) at ../nptl/sysdeps/unix/sysv/linux/pthread_getcpuclockid.c:35
#1 0x00007ffff7afe7bf in getThreadCPUUsage () from /usr/local/lib/libpilight.so
#2 0x00007ffff7b06851 in threads_cpu_usage () from /usr/local/lib/libpilight.so
#3 0x000000000040ac60 in pilight_stats ()
#4 0x000000000040b197 in main ()
(gdb) frame 0
#0 pthread_getcpuclockid (threadid=0, clockid=0x7fffffffe11c) at ../nptl/sysdeps/unix/sysv/linux/pthread_getcpuclockid.c:35
35 if (INVALID_TD_P (pd))