| Subject: | Have named log the output from named -V when logging an assertion failure and termination |
When named crashes, in most cases it logs the reason for the crash, and in a few more, it provides us with a backtrace (per:
2667. [func] Add support for logging stack backtrace on assertion
failure (not available for all platforms). [RT #19780])
And then we find ourselves asking a bunch of questions about the run-time environment and the named build and ..
As a first step towards better data collection (see also #43640: Create a tool to gather all the necessary files to accompany a core dump) can we enhance the code that is logging the crash and the stack trace, to add:
1. named -V
2. Some of the stuff about the runtime environment - perhaps what
we get from rndc status?
3. Information about the OS
I'd also suggest logging it with some nice boundaries so that it looks like a little information panel in the logfiles and it's obvious to the admins that they should make sure they send all of it to us when they report it.
We could even include in the crash logging 'panel' what it is that they should do to report it, and recommend them to report it to us directly versus discussing it in any community groups?