-
Notifications
You must be signed in to change notification settings - Fork 3
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
libheaptrace: Report self consuming memory #14
base: main
Are you sure you want to change the base?
Conversation
Current patch causes segfault.
|
To resolve this (crash) issue, I use C APIs on But after I apply
And run heaptrace on gdb with factorial.out
|
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>
d98f9cb
to
c5c0cc4
Compare
Now it works properly. Report heaptrace self consuming memory overhead, for user who want to know memory overhead. Add
|
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.