libheaptrace: Report self consuming memory - #14
Open
Bojun-Seo wants to merge 1 commit into
Open
Conversation
Collaborator
Author
|
Current patch causes segfault. |
Collaborator
Author
|
To resolve this (crash) issue, I use C APIs on But after I apply And run heaptrace on gdb with factorial.out |
Bojun-Seo
force-pushed
the
mem_overhead
branch
2 times, most recently
from
February 27, 2023 06:17
0203b93 to
d98f9cb
Compare
Report heaptrace self consuming memory overhead, for user who want to know memory overhead. Allocation requests when hook_guard is set are self allocation. Signed-off-by: Bojun Seo <bojun.seo@lge.com>
Bojun-Seo
force-pushed
the
mem_overhead
branch
from
February 27, 2023 06:25
d98f9cb to
c5c0cc4
Compare
Collaborator
Author
|
Now it works properly. Report heaptrace self consuming memory overhead, for user who want to know memory overhead. Add |
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.
Knowing memory overhead can be important in some cases
So add atomic variable to count size and report it
This patch is draft, not working yet.