Closed fhs closed 8 years ago
My first action would be to find the position of that assert and then split it apart into 6 single asserts instead of this long one where no-one knows which of the logically compounded statements is the real issue, also I find it bad style to mix && and || without parentheses.
After replacing enp0s25
with eth0
to make the script work for me (and even before), I can't reproduce your problem on debian with libc 2.21 nor 2.23, meaning it would be hard for me to debug this.
Try reducing your conkyrc to a minimal-non-working example by bisection it and testing if the error still appears.
I tried to minimize my conky config, but I couldn't reduce it in a way which points to a single part of the config. It seems like a memory corruption of some kind. I doubt this is a glibc bug. Does the valgrind output make any sense?
OK tested your conf with current Latest commit 06f87b9
and it is working just fine.
I have commented last 2 lines IPv4 and IPv6.
conky 1.10.2_pre compiled Fri Apr 22 19:22:58 IST 2016 for Linux 4.5.1-1-ARCH x86_64
I couldn't reproduce the crash with latest revision (06f87b9), so I did a git bisect. It points to commit adae1f62934311b371701ac6228b3c87f1698e0b that fixed the crash.
Fantastic So perhaps you can close this issue :)
Hoping for a new release soon :)
Conky is crashing with the following error:
This is conky 1.10.1 and glibc 2.23 in Archlinux. See below for gdb backtrace, valgrind output, and my conky.conf file. I can't reproduce the crash with the default Archlinux config.
~/.config/conky/conky.conf: