[syslog-ng] [Bug 183] Threaded Syslog-ng chashes resolving locally

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Fri Jun 8 15:17:53 CEST 2012


--- Comment #2 from Gergely Nagy <algernon at balabit.hu>  2012-06-08 15:17:53 ---
(In reply to comment #1)
> I managed to reproduce it, but the backtrace looks weird:

Right. Under gdb, it's much better:

Thread 4 (Thread 0x7ffff288f700 (LWP 22936)):
#0  0x00007ffff6261475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007ffff62646f0 in *__GI_abort () at abort.c:92
#2  0x00007ffff629b26b in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#3  0x00007ffff62a4ab6 in malloc_printerr (action=3, str=0x7ffff637b7e0 "double free or corruption (fasttop)", ptr=<optimized out>) at malloc.c:6283
#4  0x00007ffff62a97ec in *__GI___libc_free (mem=<optimized out>) at malloc.c:3738
#5  0x00007ffff7b6202f in dns_cache_destroy () at ../../lib/dnscache.c:365
#6  0x00007ffff7b7c4ca in main_loop_io_worker_thread_stop (cookie=0x0) at ../../lib/mainloop.c:324
#7  0x00007ffff7ba754c in iv_work_thread (_thr=0x622bd0) at ../../../../lib/ivykis/modules/iv_work.c:199
#8  0x00007ffff7ba7b94 in iv_thread_handler (_thr=0x622ca0) at ../../../../lib/ivykis/modules/iv_thread.c:100
#9  0x00007ffff65bcb50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#10 0x00007ffff630790d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

This seems to be the problem. I suppose dns_cache_destroy() is not guarded by a lock, while it should be.

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list