Add backtrace_full method to FullBacktraceCollector for multi-threaded trace collection
#3468
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.
Description
This PR extends the
FullBacktraceCollectorwith a newbacktrace_fullmethod to address limitations in multi-threaded environments. While trace information is collected from all threads, it's stored in the Thread Local Storage of individual threads. The existingbacktracemethod only accesses the current thread's TLS, making it impossible to retrieve traces from threads that have already terminated. The newbacktrace_fullmethod aggregates trace information from all available thread storage, including data from threads that no longer exist, ensuring complete trace collection across the entire system.Checklist
./scripts/precommit.shand addressed all comments