It looks like the problem is on line 581 of common/macros.c. Most like
the pointer is getting set to an invalid address at some point.
I've been running the b4 code with the new servicegroup macros for about
two weeks without problems thus far. I'll try running it under a
debugger with various service/servicegroup variations to see if I can
get it to segfault.
Can you run Nagios with the debug log enabled for service checks to find
out what service is being checked immediately before the segfault? If
you could send (offline if necessary) the corresponding service
definition, as well as defs for any servicegroups its a member of, that
would be helpful as well.
Andreas Ericsson wrote:
> hindrek murdsalu wrote:
>> There you go:
>>
>> Program received signal SIGABRT, Aborted.
>
> SIGABRT?
>
> Gawds, I *HATE* when libs do that "oh we crashed so we'd better
> tell te user where", as it always prevents a proper debugger from
> finding where the problem actually happened.
>
> Anyways, it seems as if something weird is happening in
> grab_servicegroup_macros() during a realloc() call, which probably
> feeds it a bogus pointer.
>
> What happens if you remove all your servicegroups and try running
> nagios then?
>
>> #5 0x00002b6b8ef6c8b8 in realloc () from /lib64/libc.so.6
>> #6 0x0000000000430192 in grab_servicegroup_macros (sg=0x72f820) at
>> ../common/macros.c:581
>
--
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]