Nagios Core Dump File

[derekbrewer]

Nagios segfaulted on us today and it produced a core file. I started looking at it a little bit, but I'm not sure exactly what to look for. A few basic commands gave me this...

(gdb) where
#0 0x00007ffff75504ad in vfprintf () from /lib64/libc.so.6
#1 0x00007ffff755b287 in vfwprintf () from /lib64/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) bt full
#0 0x00007ffff75504ad in vfprintf () from /lib64/libc.so.6
No symbol table info available.
#1 0x00007ffff755b287 in vfwprintf () from /lib64/libc.so.6
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I'm running Nagios Core 4.3.4 on RHEL7.5. I have plans to upgrade to the latest version of Nagios, but I'm not there yet. I'm really just looking to see if there's anything interesting that can be pulled out of this core file. Anyone have any good tips for this?

[mbellerue]

Unfortunately it's really difficult to get anything out of a single core dump. There are so many reasons an application could crash. Core dumps become much more useful when an application is crashing in a somewhat predictable manner. From there we can figure out a starting point and start investigating.