3.0b6 crashes with SIGSEGV

[Hendrik Bäcker]

> 
> Can you run the unstripped nagios binary under gdb and do a backtrace 
> when it segfaults?  That will help track down the source of the segfault.
> 
> 
> cd <nagios-src>/base
> gdb --args ./nagios /usr/local/nagios/etc/nagios.cfg
> r
> 
> When it segfaults, do a backtrace...
> 
> bt
> 
> and send the output.
> 

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

Regards
Hendrik

-------------------------------------------------------------------------
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/