> From: [email protected]=20
> [mailto:[email protected]] On Behalf=20
> Of Ethan Galstad
> Sent: Tuesday, November 06, 2007 12:53 PM
> To: Nagios Developers List
> Subject: Re: [Nagios-devel] 3.0b6 crashes with SIGSEGV
>=20
> Boeckman, Matthew wrote:
> >
> >> Confirmed. With the actual cvs code I got a Segfault.
> >>
> >> It seems that it is a segfaulting fork, cause gdb doesn't=20
> break the=20
> >> run, it is still running until a
> >>
> >> Here's the bt:
> >>
> >> ###
> >> Nagios 3.0b6 starting... (PID=3D24645)
> >> Local time is Tue Nov 06 19:49:48 CET 2007 [New Thread
> >> -1211335776 (LWP 24648)] Caught SIGSEGV, shutting down...
> >>
> >>
> >>
> >>
> >>
> >> bt
> >>
> >> Program received signal SIGINT, Interrupt.
> >> [Switching to Thread -1211103568 (LWP 24645)] 0xffffe410 in=20
> >> __kernel_vsyscall ()
> >> (gdb) bt
> >> #0 0xffffe410 in __kernel_vsyscall ()
> >> #1 0xb7ec0376 in ?? () from /lib/libpthread.so.0
> >> #2 0x0806d8ed in event_execution_loop () at events.c:1124
> >> #3 0x08055e2e in main (argc=3DCannot access memory at address 0x0
> >> ) at nagios.c:793
> >>
> >> (gdb) kill
> >> Kill the program being debugged? (y or n) y
> >> (gdb) q
> >>
> >> ###
> >>
> >> Interesting thing: The SIGSEGV is mentioned in the nagios.log:
> >>
> >> [1194375179] Caught SIGSEGV, shutting down...
> >> [1194375179] Caught SIGSEGV, shutting down...
> >> [1194375179] Caught SIGSEGV, shutting down...
> >> [1194375179] Caught SIGSEGV, shutting down...
> >> [1194375179] Caught SIGSEGV, shutting down...
> >> [1194375179] Caught SIGSEGV, shutting down...
> >> [1194375179] Caught SIGSEGV, shutting down...
> >>
> >=20
> > I should have mentioned that - gdb asked me to kill the running=20
> > process in exactly the same way. Similairly my nagios.log=20
> is catching=20
> > the SIGSEGV.
> >=20
> >=20
> >> Regards
> >> Hendrik
> >>
>=20
> I see I just introduced a new segfault this morning.
=20> Patch is now in CVS. If the latest CVS code still causes=20
> problems, you can debug child process segfault like this:
>=20
> gdb --args ./nagios /usr/local/nagios/etc/nagios.cfg set=20
> follow-fork-mode child r
>=20
> That will allow you to do a backtrace in the child processes=20
> if they segfault.
>=20
[New Thread -1211237488 (LWP 24010)]
[New process 24011]
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...
It loops through that SIGSEGV message until I ctrl-c out. Glibc-2.5-12
from centos5 install.=20
>=20
> Ethan Galstad
> Nagios Developer
> ___
> Email: [email protected]
> Web: www.nagios.org
>=20
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and=20
> a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]