3.0b6 crashes with SIGSEGV

[Boeckman, Matthew]

-----Original Message-----
> From: nagios-devel-bounces at lists.sourceforge.net 
> [mailto:nagios-devel-bounces at lists.sourceforge.net] On Behalf 
> Of Ethan Galstad
> Sent: Tuesday, November 06, 2007 12:53 PM
> To: Nagios Developers List
> Subject: Re: [Nagios-devel] 3.0b6 crashes with SIGSEGV
> 
> Boeckman, Matthew wrote:
> > <snip>
> >> Confirmed. With the actual cvs code I got a Segfault.
> >>
> >> It seems that it is a segfaulting fork, cause gdb doesn't 
> break the 
> >> run, it is still running until a <CTRL-c>
> >>
> >> Here's the bt:
> >>
> >> ###
> >> Nagios 3.0b6 starting... (PID=24645)
> >> Local time is Tue Nov 06 19:49:48 CET 2007 [New Thread
> >> -1211335776 (LWP 24648)] Caught SIGSEGV, shutting down...
> >>
> >> <here is still s.th. running>
> >>
> >> <here is still s.th. running>
> >>
> >> bt
> >>
> >> Program received signal SIGINT, Interrupt.
> >> [Switching to Thread -1211103568 (LWP 24645)] 0xffffe410 in 
> >> __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=Cannot 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...
> >>
> > 
> > I should have mentioned that - gdb asked me to kill the running 
> > process in exactly the same way. Similairly my nagios.log 
> is catching 
> > the SIGSEGV.
> > 
> > 
> >> Regards
> >> Hendrik
> >>
> 
> I see I just introduced a new segfault this morning. :-( 
> Patch is now in CVS.  If the latest CVS code still causes 
> problems, you can debug child process segfault like this:
> 
> gdb --args ./nagios /usr/local/nagios/etc/nagios.cfg set 
> follow-fork-mode child r
> 
> That will allow you to do a backtrace in the child processes 
> if they segfault.
> 

[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. 


> 
> Ethan Galstad
> Nagios Developer
> ___
> Email: nagios at nagios.org
> Web:   www.nagios.org
> 
> --------------------------------------------------------------
> -----------
> 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 
> a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
> 

-------------------------------------------------------------------------
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 a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/