status_server: add glibc, pthread, libgcc to the blocklist (#11205)

[YangKeao]

close #11108

Signed-off-by: YangKeao yangkeao@chunibyo.icu

What problem does this PR solve?

close #11108

Problem Summary:

If the pprof-rs sample arrives and the current program is fetching a backtrace, the program will panic. The reason is that there is a lock inside the dl_iterate_phdr, which is called while unwinding the backtrace.

A more detailed description about this problem can be found in tikv/pprof-rs#85 (comment) . In tikv, when an Error is generated, it's likely to get a backtrace and cause this problem.

After adding these libraries to the blocklist, it will also be able to turn on the heap profiling and pprof-rs cpu profiling at the same time, but I haven't modified (and tested) it yet.

What is changed and how it works?

What's Changed:

Skip all samples inside the glibc, pthread and libgcc.

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tidb-ansible:
• Need to cherry-pick to the release branch

Check List

Side effects

The sample in the libc, libgcc and pthread will not be collected in the profiling result.

Release note

status_server: skip profiling sample in glibc, pthread, libgcc to avoid possible deadlock 
status_server: upgrade pprof-rs to fix memory leak

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• BusyJay
• sticnarf

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[YangKeao]

/cc @sticnarf
/cc @BusyJay

[zhouqiang-cl]

/merge

[ti-chi-bot]

@zhouqiang-cl: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 7ee6e24

[sticnarf]

/merge

[ti-chi-bot]

@sticnarf: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@YangKeao: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.