-
Notifications
You must be signed in to change notification settings - Fork 48
feat: record stacktrace for objects allocated in stack #76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Lslightly
wants to merge
15
commits into
cloudwego:main
Choose a base branch
from
Lslightly:stackvar-location
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
e9db062
fix(pkg/proc): add mapping id in location in protobuf
Lslightly 49eca3b
simply add stacktrace to pprofIndex
Lslightly 6e9aaad
fix: avoid sharing pprofIndex node in stacktrace forest
Lslightly ec948c4
feat: add stk_obj_split dummy frame to split stacktrace and object re…
Lslightly 6d26613
remove G<id> in the top of flamegraph
Lslightly 34d9fd7
test: add StackTraceScenario
Lslightly 6176ded
refactor: rename StackTraceObjSplitLine with ReferenceStackBoundary
Lslightly 8ae7f8e
simplify stacktrace to function-level
Lslightly e1cc226
refactor: replace depth -1 with stackTracePprofIndexDepth const
Lslightly 79e2686
refactor: remove unused field
Lslightly 3403302
fix: add nil-safe helper to get function name of stackframe
Lslightly 038b25d
refactor: remove dummy mapping id
Lslightly bb0106a
refactor: recover order of flushReference and location, function writing
Lslightly c3566f0
refactor: replace nil stackframe's name to <nil>
Lslightly 882d634
test: add sample count/size comparison
Lslightly File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow comment above.
Take
main.foo -call-> main.baras an example. The count/size of samples is recorded in bothmain.fooandmain.barStackSampleNode.The other alternative is to remain
main.foo'sCount/Sizenil while keepingmain.bar'sCount/Sizethe sample's count/value.For testing purpose, both are acceptable in my opinion. The second option only simplifies the testcase without the need to write the expected count/size for each stack frame node.