[prev in list] [next in list] [prev in thread] [next in thread] 

List:       syslog-ng
Subject:    Re: [syslog-ng]Core
From:       Balazs Scheidler <bazsi () balabit ! hu>
Date:       2001-02-01 9:30:59
[Download RAW message or body]

> Syslog-ng dumped on the 29th, and  running gdb --core=core gives the
> following.  What's signal 6?  Any ideas appreciated.
> 
> 
> Core was generated by `syslog-ng -f /usr/local/etc/syslog-ng.conf -p
> /var/run/syslog-ng.pid'.
> Program terminated with signal 6, Aborted.
> #0  0x40068dd1 in ?? ()
> 
> This is on a redhat 7.0 box.  Syslog-ng 1.4.10.  Thanks...

A backtrace would be a bit more useful (bt command in gdb). Even more useful
would be a backtrace with debug information compiled in (--with-debug
configure option for both libol and syslog-ng)

A syslog-ng binary and the core file itself could also help (make sure they
don't contain sensitive information)

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1

_______________________________________________
syslog-ng maillist  -  syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng

[prev in list] [next in list] [prev in thread] [next in thread]