added experimental backtrace API #19552
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
by sending the arangod process a SIGUSR1 signal, it will make all its threads log a backtrace. it does so by enumerating the list of current threads via reading the fds in `/proc/<pid>/task` and using the `tgkill` syscall to deliver a SIGUSR2 signal to each thread. when a thread receives a SIGUSR2 signal, it will log its own backtrace to the log. this functionality is currently only available on Linux. it is highly experimental and may not work in some environments (e.g. libmusl builds).
|
Closing this PR in favor of proper safer tools such as |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scope & Purpose
Experimental backtrace API for the threads in an arangod process.
By sending the arangod process a SIGUSR1 signal, it will make all its threads log a backtrace. It does so by enumerating the list of current threads via reading the fds in
/proc/<pid>/taskand using thetgkillsyscall to deliver a SIGUSR2 signal to each thread. When a thread receives a SIGUSR2 signal, it will log its own backtrace to the log.This functionality is currently only available on Linux. it is highly experimental and may not work in some environments (e.g. libmusl builds).
Checklist
Related Information