Extending thread description#1997
Merged
Merged
Conversation
- this will give threads which run local functions (not actions) identification in debugging and profiling contexts
120514d to
771e637
Compare
Contributor
Author
e7bc3d2 to
58ac249
Compare
a78ea8a to
f41372c
Compare
Contributor
Author
|
@khuck wrote in an email:
I'll go ahead and merge this. Please report problems as new tickets. |
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.
This PR is meant to improve the diagnostic capabilities of debuggers and tracing tools (like APEX). Especially tools like APEX have a hard time associating pieces of code with events they are hooked into. By passing the addresses of scheduled (local) functions to the tool we allow to establish that missing connection (the address can be resolved to the corresponding symbol using debug information, if available).