tree 9d660460b504a7c879c6a1e7ad7986689ee59818
parent a8459b28c32c95898916c073b5ffb616eb86862f
author Willy Tarreau <w@1wt.eu> 1611321346 +0100
committer Willy Tarreau <w@1wt.eu> 1611321514 +0100
encoding latin1

MEDIUM: debug: now always print a backtrace on CRASH_NOW() and friends

The purpose is to enable the dumping of a backtrace on BUG_ON(). While
it's very useful to know that a condition was met, very often some
caller context is missing to figure how the condition could happen.
From now on, on systems featuring backtrace, a backtrace of the calling
thread will also be dumped to stderr in addition to the unexpected
condition. This will help users of DEBUG_STRICT as they'll most often
find this backtrace in their logs even if they can't find their core
file.

A new "debug dev bug" expert-mode CLI command was added to test the
feature.