Bug #4033
Segfault: Mutex not held at src/idnode.c:102 (GDB trace attached)
Start date:
2016-10-22
Due date:
% Done:
100%
Estimated time:
Found in version:
Latest git
Affected Versions:
Description
I've had this crash a few times while working on the docs, I'm not sure what causes it but it always seems to when avahi gets configured, but the error is in inode, so, I dunno, shrug.
Here's the non-gdb crash log lines:
016-10-22 12:27:03.164 [ NOTICE] START: HTS Tvheadend version 4.1-2308~gbbd61a7 started, running as PID:9788 UID:1000 GID:1000, CWD:/home/mark/Dev/git/tvheadend/mpmc/master CNF:/tmp/tvh2 Mutex not held at src/idnode.c:102 2016-10-22 12:27:03.165 [ ALERT] CRASH: Signal: 6 in PRG: ./build.linux/tvheadend (4.1-2308~gbbd61a7) [53e3902762701f8847f9a81c14d29801d73b58bb] CWD: /home/mark/Dev/git/tvheadend/mpmc/master 2016-10-22 12:27:03.165 [ ALERT] CRASH: Fault address 0x3e80000263c (N/A) 2016-10-22 12:27:03.166 [ ALERT] CRASH: Loaded libraries: /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/x86_64-linux-gnu/liburiparser.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/librt.so.1 /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libsystemd.so.0 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libselinux.so.1 /lib/x86_64-linux-gnu/liblzma.so.5 /lib/x86_64-linux-gnu/libgcrypt.so.20 /lib/x86_64-linux-gnu/libpcre.so.3 /lib/x86_64-linux-gnu/libgpg-error.so.0 2016-10-22 12:27:03.167 [ ALERT] CRASH: Register dump [23]: 00007feb96ffd70000000000000000230000000000000008000000000000020600005564230f8b1000005564218b91a80000000000000000000055642180f0ce000000000000263c000000000000264500000000000000000000556421b8bb400000000000000006000000000000000000007feb9ea2641800007feb96ffc78800007feb9ea264180000000000000206000000000000003300000000000000000000000000000000fffffffe7ffbba130000000000000000 2016-10-22 12:27:03.167 [ ALERT] CRASH: STACKTRACE 2016-10-22 12:27:03.180 [ ALERT] CRASH: ??:0 0x556421738b8d 2016-10-22 12:27:03.183 [ ALERT] CRASH: ??:0 0x7feb9f2dc3d0 2016-10-22 12:27:03.184 [ ALERT] CRASH: gsignal+0x38 (/lib/x86_64-linux-gnu/libc.so.6) 2016-10-22 12:27:03.184 [ ALERT] CRASH: abort+0x16a (/lib/x86_64-linux-gnu/libc.so.6) 2016-10-22 12:27:03.187 [ ALERT] CRASH: ??:0 0x5564216ef9ea 2016-10-22 12:27:03.190 [ ALERT] CRASH: ??:0 0x5564216fb8f6 2016-10-22 12:27:03.193 [ ALERT] CRASH: ??:0 0x5564217c3007 2016-10-22 12:27:03.195 [ ALERT] CRASH: ??:0 0x55642173ac37 2016-10-22 12:27:03.198 [ ALERT] CRASH: ??:0 0x5564216f5b5b 2016-10-22 12:27:03.201 [ ALERT] CRASH: ??:0 0x556421700765
Thankfully I did manage to capture the crash again after restarting the local build a number of times (once I'd installed corekeeper), the log is attached.
Files
History
Updated by Jaroslav Kysela over 8 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|c003ff3bf9be8a59c65f41a74dce6bd42ab2e154.