66832e3a introduced change that prints core dumps like this:
That's completely out of user-friendliness but serves as a measure for debugging hard-reproducible bugs. The proper way to implement this:
1. it must be controlled by command-line and environment variable;
2. detailed traces must be default for buildbots only, for user invocations normal stack traces should be printed.
MTR_PRINT_CORE and --print-core can accept the following values:
|no||Don't print core|
|short||Print normal trace like `bt` does|
|detailed||Print detailed stack trace like in commit 66832e3a|
|custom:<code>||Use GDB commands <code> to print stack trace|
Should be detected by environment. If BUILDMASTER environment is non-null, defaults to "detailed", otherwise "short".
Wrong values are silently ignored (falls back to default behaviour).
Overrides default behavior.
When specified without value defaults to "short". Wrong values fail execution with error.
Overrides environment variable.
|MTR hangs after multiple failures||Closed|
|MTR doesn't print stack trace for bootstrap crashes||Closed|