Hi, I have cross compiled syslog-ng-2.0.5 for 64bit mips processor. I am using glib-2.12.13. syslog-ng server crashes at startup. Here is the stack trace of the crash: Reading symbols from /lib64/libnsl.so.1...done. Loaded symbols for /lib64/libnsl.so.1 Reading symbols from /lib64/librt.so.1...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /syslog-ng/lib/libglib-2.0.so.0...done. Loaded symbols for /syslog-ng/lib/libglib-2.0.so.0 Reading symbols from /syslog-ng/lib/libevtlog.so.0...done. Loaded symbols for /syslog-ng/lib/libevtlog.so.0 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/libpthread.so.0...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/ld.so.1...done. Loaded symbols for /lib64/ld.so.1 Core was generated by `./syslog-ng -v -d -F -f /syslog-ng/syslog-ng.conf'. Program terminated with signal 11, Segmentation fault. #0 0x0000005555bd9a30 in free () from /lib64/libc.so.6 (gdb) bt #0 0x0000005555bd9a30 in free () from /lib64/libc.so.6 #1 0x000000012000e6a8 in log_msg_clear_matches (self=0x120133e10) at logmsg.c:512 #2 0x000000012000f790 in log_msg_unref (self=0x120133e10) at logmsg.c:532 #3 0x0000000120012984 in log_writer_fd_dispatch (source=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at logwriter.c:324 #4 0x00000055558cdf84 in IA__g_main_context_dispatch (context=0x120133560) at gmain.c:2045 #5 0x00000055558d1a68 in g_main_context_iterate (context=0x120133560, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2677 #6 0x00000055558d2298 in IA__g_main_context_iteration (context=0x120133560, may_block=1) at gmain.c:2736 #7 0x0000000120006b34 in main_loop_run (cfg=0xffffc61930) at main.c:164 #8 0x000000012000715c in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:426 Thanks for the help in advance. -Shashank
On Thu, 2007-10-25 at 18:09 -0700, Shashank Vinchurkar wrote:
Hi,
I have cross compiled syslog-ng-2.0.5 for 64bit mips processor. I am using glib-2.12.13. syslog-ng server crashes at startup. Here is the stack trace of the crash:
Core was generated by `./syslog-ng -v -d -F -f /syslog-ng/syslog-ng.conf'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000005555bd9a30 in free () from /lib64/libc.so.6
(gdb) bt
#0 0x0000005555bd9a30 in free () from /lib64/libc.so.6
#1 0x000000012000e6a8 in log_msg_clear_matches (self=0x120133e10) at logmsg.c:512
This is pretty bad. If it crashed in free(), it usually indicates some kind of heap corruption. Could you display the contents of *self in frame 1? E.g. something like this: (gdb) frame 1 (gdb) p *self The bad news about heap corruptions is that it is very difficult to track down without a way to reproduce it locally. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Shashank Vinchurkar