[syslog-ng]segfault signal 11, core dump, 1.5.26, 1.6.0rc1

narancs syslog-ng@lists.balabit.hu
Tue, 15 Apr 2003 15:47:27 +0200


Balazs Scheidler =EDrta:

>On Fri, Apr 11, 2003 at 01:37:13PM +0200, narancs wrote:
> =20
>
>please compile libol and syslog-ng with symbols (--enable-debug for both
>libol and syslog-ng configure script), have syslog-ng dump core and do
>
done, iboth are compiled with --enable-debug, and install the new pkg.

>
>gdb syslog-ng -c core
>gdb) bt
>
the core dump is currently 14Mb and has thousands of lines by 'bt' like=20
this:
#3094 0x3243ae3 in ?? ()
#$line_num $hex_code in ?? ()

>
>the results of the backtrace command is useful for finding the problems.
>
in this situation it does not seem to be :-(
what are the possible errors that make this core dump unusable?
the kernel has the grsec patch added, but /sbin/syslog-ng has
chpax -srmp flags (means PaX functions are disabled for this process).


what's next please?