That latest was from CVS checkout at 13:02 mountain. My original post
was based on the 3.0b6 tarball available on nagios.org.
-Matthew=20
> -----Original Message-----
> From: Ethan Galstad [mailto:[email protected]]=20
> Sent: Tuesday, November 06, 2007 1:49 PM
> To: Boeckman, Matthew; Nagios-Devel
> Subject: Re: [Nagios-devel] 3.0b6 crashes with SIGSEGV
>=20
> Boeckman, Matthew wrote:
> [snip]
> >>
> >> gdb --args ./nagios /usr/local/nagios/etc/nagios.cfg set=20
> >> follow-fork-mode child r
> >>
> >> That will allow you to do a backtrace in the child=20
> processes if they=20
> >> segfault.
> >>
> >=20
> > [New Thread -1211237488 (LWP 24010)]
> > [New process 24011]
> >=20
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to process 24011]
> > 0x009b1202 in vasprintf () from /lib/libc.so.6
> > (gdb) Caught SIGSEGV, shutting down...
> > Caught SIGSEGV, shutting down...
> > Caught SIGSEGV, shutting down...
> > Caught SIGSEGV, shutting down...
> > Caught SIGSEGV, shutting down...
> >=20
> > It loops through that SIGSEGV message until I ctrl-c out.=20
> Glibc-2.5-12=20
> > from centos5 install.
> >=20
> >=20
>=20
> Quick question - are you using the standard 3.0b6 release or=20
> did you grab the CVS code this morning? If so, make sure you=20
> have the latest CVS code as I just patched a bug.
>=20
>=20
> Ethan Galstad
> Nagios Developer
> ___
> Email: [email protected]
> Web: www.nagios.org
>=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]