On Thu, Nov 14, 2002 at 06:07:02PM +0100, Balazs Scheidler wrote:
can you analyze the core a bit more? (it is no use to send it to me, as it might contain libc different from my system)
gdb syslog-ng -c core (gdb) frame 4
this selects the frame of xalloc()
now display part of the stack:
p $ebp x/40 $ebp-20
I'll try to find how many bytes c_format_() wants to allocate. This might help to track down the problem.
Is that of any help for you? (gdb) frame 4 #4 0x080530a7 in xalloc () (gdb) p $ebp $1 = (void *) 0xbfffe868 (gdb) x/40 $ebp-20 0xbfffe854: 0x00000098 0x4014afa0 0x00000000 0xcedfcc12 0xbfffe864: 0xcedfcc12 0xbfffe888 0x080531f7 0xcedfcc21 0xbfffe874: 0x4014afa0 0xcedfcc12 0x0000003b 0x08075ce0 0xbfffe884: 0x0000003b 0xbfffe8b8 0x0805068f 0xcedfcc12 0xbfffe894: 0xbfffe8c4 0xbfffe8b8 0x4009f548 0x08075b70 0xbfffe8a4: 0x0806c224 0xbffff8e8 0x0000003b 0x08075ce0 0xbfffe8b4: 0x080817ac 0xbffff8f8 0x08053501 0x080540bd 0xbfffe8c4: 0xcedfcc12 0x3927911d 0x00000000 0x0806f5ac 0xbfffe8d4: 0x31203431 0x00001000 0x080691a8 0x3e32323c 0xbfffe8e4: 0x20766f4e 0x31203431 0x30303a33 0x2034323a
This code is different in libol 0.3 (thus in syslog-ng 1.5) so it might be more stable.
1.5.x itself seems to be solid (I don't know any pending problems now, other than minor cosmetic changes like the configure script)
So far I didn't experience any crashes, and judging by the MRTG graphs based on the syslog entries, it seems to cope with the load. Thanks for your help so far, he