[syslog-ng] Syslog-ng Dies - core dump

[Balazs Scheidler]

On Fri, Jun 02, 2000 at 10:52:37AM -0400, John Wingenbach wrote:
> I have upgraded the syslog-ng to V1.4.4 and am still seeing syslog-ng croak:
> 
> falcon#> gdb /opt/syslog-ng/sbin/syslog-ng
> GNU gdb 4.17
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "sparc-sun-solaris2.6"...
> (gdb) r -dv
> Starting program: /opt/syslog-ng/sbin/syslog-ng -dv
> [New LWP    2        ]
> [New LWP    3        ]
> [New LWP    4        ]
> binding fd 8, inetaddr: 0.0.0.0, port: 514
> io.c: Preparing fd 8 for reading
> syslog-ng version 1.4.4 starting
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x2b778 in ol_object_check (class=Cannot access memory at address 0xef7ffff4.
> ) at xalloc.c:241
> xalloc.c:241: No such file or directory.
> (gdb) bt
> #0  0x2b778 in ol_object_check (class=Cannot access memory at address
> 0xef7ffff4.
> ) at xalloc.c:241
> Cannot access memory at address 0xef7fff7c.

a real backtrace would be helpful. I mean compile both libol and syslog-ng
with the --with-debug configure option, recompile, reproduce the problem and
send me a backtrace.

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
     url: http://www.balabit.hu/pgpkey.txt