Add example illustrating look up of mangled symbols #831
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
Most symbol sources store mangled symbol names. Hence, the mangled name is what the Inspector::lookup facility matches against. However, that is not always desired. Rather, sometimes filtering needs happen based on the demangled name or other information encoded in the mangled symbol (such as number of function arguments). We support this use case via the Inspector::for_each functionality, but it's not trivially obvious that this is possible to begin with. With this change we add an example that illustrates such usage. Signed-off-by: Daniel Müller <[email protected]>
danielocfb
force-pushed
the
topic/inspect-demangle
branch
from
8f1b5c2
to
b24fd57
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #831 +/- ##
=======================================
Coverage 94.78% 94.78%
=======================================
Files 52 52
Lines 9830 9830
=======================================
Hits 9317 9317
Misses 513 513 ☔ View full report in Codecov by Sentry. |
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.
Most symbol sources store mangled symbol names. Hence, the mangled name is what the Inspector::lookup facility matches against. However, that is not always desired. Rather, sometimes filtering needs happen based on the demangled name or other information encoded in the mangled symbol (such as number of function arguments).
We support this use case via the Inspector::for_each functionality, but it's not trivially obvious that this is possible to begin with. With this change we add an example that illustrates such usage.