Core file?

[Jim Reid]

>>>>> "Johnny" == Johnny Damtoft <JOD at sonofon.dk> writes:

    Johnny> One of my bind9 servers has been crashing some times now,
    Johnny> and it makes a core file.

Please report this to bind9-bugs at isc.org. Don't mail the core dump,
but keep it handy in case someone wants to look at it. If the debugger
can provide a stack backtrace, providing that in your bug report would
be useful. Be sure to include info about the BIND and OS versions in
your bug report. If there are relevant error messages in the logs --
for example an assertion failure report -- supply them too. Provide
other background info that might be helpful: for instance if the crash
is reproducible or predictable in some way.

    Johnny> Can i use the corefile for something usefull? Like see
    Johnny> what the error might be? or which IP that made this
    Johnny> nameserver to crash and make the corefile?  Any kind of
    Johnny> information that i can get out of it?

A system debugger like gdb should be able to analyse the core dump and
show what was in the name server's internal data structures. That
information is probably only going to be useful to a developer or
someone else who knows their way around the code. They might be able
to identify the cause of the crash -- not necessarily an IP whatever
that is (I presume you mean client IP address) -- by picking through
the core dump with the debugger. However some debuggers don't work on
core dumps from threaded applications, like BIND9.