Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List coredumps of the Manager & child process of Varnish. This contains useful information such as: time of the crash, pid, uid, gid, signal, whether corefile is present, path of the executeable and size of the corefile.
Gather further information of each coredump, such as but not limited to: command line, cgroup, stack traces of threads, loaded so, path of the corefile.
Coredump analysis of the latest crash is done using coredumpctl, we invoke gdb on the coredump to get the backtrace. This depend on coredumpctl having --debugger-arguments.
A debug mode is introduced and activated through "-d", when activated we invoke gdb on all Varnish instances to get full backtrace and threads information. This is behind a non-default flag as it will pause Varnish while gathering this information.
Signed-off-by: Asad Sajjad Ahmed asadsa@varnish-software.com