#19524 does not handle SIGABRT deliberately.
Because there should not be the cases when we cannot print our own diagnostics.

I see the motivation here: #19580 (comment), let's try...

This is also required in other places (like fast-test - https://clickhouse-test-reports.s3.yandex.net/20477/8ad20fcee5aaa642c2a2dd873d02103692d554f4/fast_test.html#fail1)

Note that it should not prevent receiving fatal messages with stack trace in client.

Note that it should not prevent receiving fatal messages with stack trace in client.

Right. Actually I don't think that this should break this, since the server will continue after gdb will print stacktraces

Stress tests are okay, but fasttest not:

https://clickhouse-test-reports.s3.yandex.net/20462/014c11af7fcaa60d62c10b1497bbdc02526d180c/fast_test/runlog.out.log

/ClickHouse/docker/test/fasttest/run.sh: line 121: gdb: command not found

By some reason fasttest image wasn't updated, because that layer was in cache https://clickhouse-test-reports.s3.yandex.net/20462/014c11af7fcaa60d62c10b1497bbdc02526d180c/push_to_dockerhub/taglatest.out.1.log

 ---> Using cache
 ---> 9446b5f83627
Step 6/17 : RUN apt-get update     && apt-get install         apt-transport-https         bash         brotli         build-essential         ca-certificates         ccache         clang-${LLVM_VERSION}         clang-tidy-${LLVM_VERSION}         cmake         curl         lsof         expect         fakeroot         git         gdb         gperf         lld-${LLVM_VERSION}         llvm-${LLVM_VERSION}         moreutils         ninja-build         psmisc         python3         python3-pip         python3-lxml         python3-requests         python3-termcolor         rename         software-properties-common         tzdata         unixodbc        --yes --no-install-recommends
 ---> Using cache

72c61da does not helps with avoiding using docker cache for "new" layers, maybe it should be reset somehow? (@alesapin ?)

Lack of backtrace in stress tests happens one more time - https://clickhouse-test-reports.s3.yandex.net/20477/18a147b3179e5931d89395d5e46b4d833d4bef05/stress_test_(memory).html#fail1

72c61da does not helps with avoiding using docker cache for "new" layers, maybe it should be reset somehow? (@alesapin ?)

Let's try install it as a separate layer then - c879719e7c1ed188cdd81a73148575cdbbacaf13

Let's try install it as a separate layer then - c879719

Still no luck, moved into separate PR - #20864

Marker check Pending — Starting checks (No special conditions apply)

Looks hanged

@alexey-milovidov can you merge this? (maybe it will reproduce the problem and will have full stacktrace, in the meantime I will look into this #16481 (comment))