23.8 Backport #63865 fix SIGSEGV due to profiler to 23.8.16

[shiyer7474]

Original PR : ClickHouse#63865

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Fix SIGSEGV due to CPU/Real (query_profiler_real_time_period_ns/query_profiler_cpu_time_period_ns) profiler (has been an issue since 2022, that leads to periodic server crashes, especially if you were using distributed engine)

Fixes: ClickHouse#60460
Fixes: ClickHouse#33531
Fixes: ClickHouse#60219
Refs: ClickHouse/libunwind#25
Refs: llvm/llvm-project#92291

Documentation entry for user-facing changes

[altinity-robot]

This is an automated comment for commit 034c9f6 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
ClickHouse build check	Builds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process	✅ success
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	✅ success
Docker image for servers	The check to build and optionally push the mentioned image to docker hub	✅ success
Install packages	Checks that the built packages are installable in a clear environment	✅ success
Push to Dockerhub	The check for building and pushing the CI related docker images to docker hub	✅ success
Ready for release	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success

Check name	Description	Status
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	⏳ pending
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	❌ failure
Mergeable Check	Checks if all other necessary checks are successful	❌ failure
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ failure
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	❌ failure

[shiyer7474]

Analyzed CI failures, too many of them, but failures looks similar to or better than another PR that was just merged into 23.8.16

This PR #466 : https://s3.amazonaws.com/altinity-build-artifacts/466/034c9f62db9685d95e6516a0882e376c52955cf6/ci_running.html
Earlier PR #465 : https://s3.amazonaws.com/altinity-build-artifacts/465/5fd626168226b0c00e9f889f433fe3d5322b71a1/ci_running.html

Kerberos tests have failed in multiple Integration test suites (test_storage_kerberized_hdfs). Test 02920* variants have failed in many stateless suites. Stress test failure is same in PR 466 & 465.