[syslog-ng] [Bug 18] random signal 6 in raise() from libc

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=18





--- Comment #1 from Anders Henke <anders.henke at 1und1.de>  2008-02-01 15:25:10 ---
Ouch, the backtrace has been missing ...

#0  0x00007fea95e9a07b in raise () from /lib/libc.so.6
#1  0x00007fea95e9b84e in abort () from /lib/libc.so.6
#2  0x00000000004237db in g_logv ()
#3  0x0000000000423861 in g_log ()
#4  0x00000000004226ea in g_malloc0 ()
#5  0x000000000040de0c in log_msg_new (
    msg=0x7fea94f36f50 "<43> syslog-ng[16915]: gmem.c:172: failed to allocate 128 bytes\n", length=64, saddr=0x0, flags=6, bad_hostname=0x0) at logmsg.c:648
#6  0x00000000004051fd in msg_send_internal_message (prio=43, 
    msg=0x7fea94f34130 "gmem.c:172: failed to allocate 128 bytes")
    at messages.c:59
#7  0x0000000000405400 in msg_log_func (log_domain=0x445eb2 "GLib", 
    log_flags=6, 
    msg=0x7fea94f34130 "gmem.c:172: failed to allocate 128 bytes", 
    user_data=0x0) at messages.c:112

Ok, the abort seems to relate to an out of memory condition; I'm running syslog-ng with ulimits (128M) to 
prevent syslog-ng from screwing up the box due to some memory leak (I've quite often seen memory leaks,
but didn't yet have the time to check them back). I'll be tracing it in valgrind over the weekend ...


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