Dear Maintainer,

I'm experiencing an apparently random segfault of conky-std
version: Conky 1.9.0 compiled Fri May 11 06:08:41 UTC 2012 for Linux
2.6.32-5-amd64 (x86_64)

Dmesg says "conky[14384]: segfault at 25 ip 00007f491c56baba sp
00007fff548509b0 error 4 in libc-2.13.so[7f491c527000+17d000]"

# dpkg -l | grep libc6
ii  libc6:amd64      2.13-35   amd64    Embedded GNU C Library: Shared
libraries
ii  libc6-dev:amd64  2.13-35   amd64    Embedded GNU C
Library: Development Libraries and Header Files
ii  libc6-i386       2.13-35   amd64    Embedded GNU C Library: 32-bit
shared libraries for AMD64
ii  libcompfaceg1  1:1.5.2-5   amd64    Compress/decompress images for
mailheaders, libc6 runtime

Attached you're going to find the conky config file.

I'm at your disposal for further infos
Thank you very much
Luca Sighinolfi

found 692199 1.9.0-2
tag 692199 + moreinfo
thanks

Hi Luca,

Would it be possible for you to get a backtrace [1]? Unfortunately
debug packages aren't provided for conky yet (that's on my todo list),
so you'll have to rebuild the package as instructed on that Debian
wiki page.

Regards,
Vincent

[1] http://wiki.debian.org/HowToGetABacktrace

Hi Vincent,

I've launched conky using gdb.
This is the result.

  ~:$ gdb conky
 GNU gdb (GDB) 7.4.1-debian
 Copyright (C) 2012 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".
 For bug reporting instructions, please see:
 <http://www.gnu.org/software/gdb/bugs/>...
 Reading symbols from /usr/bin/conky...done.
 (gdb) run -c ~/.conky/conkyrc
 Starting program: /usr/bin/conky -c ~/.conky/conkyrc
 [Thread debugging using libthread_db enabled]
 Using host libthread_db library
  "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffefec4700
  (LWP 17333)] [New Thread 0x7fffef6c3700 (LWP 17334)]
 [New Thread 0x7fffeeec2700 (LWP 17335)]
 [New Thread 0x7fffee6c1700 (LWP 17336)]
 [New Thread 0x7fffedec0700 (LWP 17337)]
 [New Thread 0x7fffed6bf700 (LWP 17338)]
 [New Thread 0x7fffecebe700 (LWP 17339)]
 [New Thread 0x7fffec6bd700 (LWP 17340)]
 Conky: desktop window (bd) is root window
 Conky: drawing to desktop window
 Conky: drawing to double buffer

<<< maybe after one day of correct functioning >>>

 Program received signal SIGSEGV, Segmentation fault.
 0x00007ffff4c3aaba in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6

Then the backtrace

 (gdb) bt
 #0 0x00007ffff4c3aaba in vfprintf ()from /lib/x86_64-linux-gnu/libc.so.6
 #1 0x00007ffff4c614a2 in vsnprintf ()from /lib/x86_64-linux-gnu/libc.so.6
 #2 0x00007ffff4c43313 in snprintf ()from /lib/x86_64-linux-gnu/libc.so.6
 #3 0x000000000045d61b in print_top (obj=0x6d2ee0, p=0x6d33c3 "", p_max_size=15613)
 at ../../src/top.c:1002
 #4 0x0000000000430b25 in generate_text_internal (p=0x6d33c3 "", p_max_size=15613,
     root=..., cur=0x685bc0) at ../../src/conky.c:2184
 #5 0x00000000004317b8 in generate_text () at ../../src/conky.c:2427
 #6 0x0000000000435424 in update_text () at ../../src/conky.c:3455
 #7 0x00000000004357ff in main_loop () at ../../src/conky.c:3546
 #8 0x000000000043d265 in main (argc=3, argv=0x7fffffffe528)
 at ../../src/conky.c:5957

Sorry for the late reply... at the beginning of the tests, there was
the option "background on" in conkyrc that resulted in no backtrace from
gdb.

At the moment, conky faults with segfault about every day.
Consider that the PC is on h24.

I hope this help you to find a good solution!!
Conky is a very usefull program; without its informations printed on the
screen, I feel blind :-)

If you need more informations, just ask!

Thank you
Ciao

tag 692199 - moreinfo
forwarded 692199 https://sourceforge.net/support/tracker.php?aid=3587680
thanks

On Thu, Nov 15, 2012 at 10:38 AM, Luca Sighinolfi <lsighinolfi@autistici.org> wrote:

Thanks! I've forwarded this bug report upstream (see [1]), and I'll
let you know if I or conky's developers need any more information.

Regards,
Vincent

[1] https://sourceforge.net/support/tracker.php?aid=3587680

Hi Luca,

thanks for the backtrace. Could you also try running conky in valgrind
and attach any errors it discovers? I don't know if one needs any
special setup on debian, but normally just running "valgrind conky"
would suffice (you need conky with debug symbols).

regards,
pl