External Commands segfault

[David Schlecht]

Hi All

Doing a stack dump on Nagios after a segfault following an External Command gives the following stack. Does this make sense to anyone? Where do I go from here? Again, this happens on all tested platforms, all Nagios versions, and all tested Linux.

===========
Detaching after fork from child process 19947.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208391264 (LWP 5431)]
0x0806c951 in hashfunc2 (name1=0x2 <Address 0x2 out of bounds>,
    name2=0x80f <Address 0x80f out of bounds>, hashslots=1024) at utils.c:4285
4285                    for(i=0;i<strlen(name1);i++)
(gdb)
(gdb) bt
#0  0x0806c951 in hashfunc2 (name1=0x2 <Address 0x2 out of bounds>,name2=0x80f <Address 0x80f out of bounds>, hashslots=1024) at utils.c:4285
#1  0x080768a1 in find_service (host_name=0x2 <Address 0x2 out of bounds>,svc_desc=dwarf2_read_address: Corrupted DWARF expression.
) at ../common/objects.c:5016
#2  0x0808ef4b in handle_scheduled_downtime (temp_downtime=0x9f21c00)    at ../common/downtime.c:311
#3  0x08063454 in handle_timed_event (event=0x9fa2728) at events.c:1289
#4  0x08063a9d in event_execution_loop () at events.c:964
#5  0x0805394d in main (argc=3, argv=0xbff3f274) at nagios.c:710
(gdb)





- David Schlecht (dschl)

-----------------------
The mailing list archive is found here:
http://www.nagiosexchange.org/nagios-users.34.0.html
				

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null