>
>> 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
>>
>> 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...
>>
>>
>>
>>
>>
>> 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 inCVS. 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.
Ethan Galstad
Nagios Developer
___
Email: [email protected]
Web: www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]