Nagios 3.0 RC2: Segmentation faults after starting

[Christian Schneemann]

Hallo,
our test Nagios dies after every restart with a segmentation fault since last 
week.
I have tried to find the error with gdb. I hope someone can point me to my 
error.


d139:/etc/nagios/objects/hosts # 
gdb --args /usr/sbin/nagios /etc/nagios/nagios.cfg 
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...
(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) run
Starting program: /usr/sbin/nagios /etc/nagios/nagios.cfg
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47105982427648 (LWP 15658)]
(no debugging symbols found)
(no debugging symbols found)

Nagios 3.0rc2
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 01-29-2008
License: GPL

Nagios 3.0rc2 starting... (PID=15658)
Local time is Tue Feb 12 10:37:24 CET 2008
[New Thread 1082132800 (LWP 15661)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47105982427648 (LWP 15658)]
0x000000000043b90a in process_check_result_queue ()
(gdb) bt
#0  0x000000000043b90a in process_check_result_queue ()
#1  0x000000000041c536 in reap_check_results ()
#2  0x0000000000429119 in handle_timed_event ()
#3  0x0000000000429701 in event_execution_loop ()
#4  0x00000000004120fe in main ()
(gdb) s
Single stepping until exit from function process_check_result_queue, 
which has no line number information.
0x0000000000437c50 in sighandler ()
(gdb) s
Single stepping until exit from function sighandler, 
which has no line number information.
Caught SIGSEGV, shutting down...
0x00002ad7b7394c10 in __restore_rt () from /lib64/libc.so.6
(gdb) s
Single stepping until exit from function __restore_rt, 
which has no line number information.
0x000000000043b90a in process_check_result_queue ()
(gdb) s
Single stepping until exit from function process_check_result_queue, 
which has no line number information.

Program received signal SIGSEGV, Segmentation fault.
0x000000000043b90a in process_check_result_queue ()
(gdb)




Regards
-- 
Christian Schneemann

-------------------------------------
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg

Phone:  +49 (0)911 - 740 53 0
e-mail: cschneemann at suse.de
-------------------------------------
SUSE LINUX Products GmbH, GF: Markus Rex
HRB 16746 (AG Nürnberg)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/