feat(symbolizer): Symbolize thread start address - #401
Merged
Conversation
rabbitstack
force-pushed
the
thread-start-address-symbol
branch
from
December 11, 2024 19:22
1a529d0 to
02ca983
Compare
Resolve the thread start address to its respective symbol name and the module from which the function call is originated.
rabbitstack
force-pushed
the
thread-start-address-symbol
branch
from
December 12, 2024 20:20
02ca983 to
62b2ff1
Compare
This file contains hidden or 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
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.
What is the purpose of this PR / why it is needed?
Resolve the thread start address to its respective symbol name and the module from which the function call is originated.
What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
/kind improvement
Any specific area of the project related to this PR?
/area instrumentation
Special notes for the reviewer
Does this PR introduce a user-facing change?