Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Total size mismatches #4

Open
nikolaydubina opened this issue Mar 9, 2022 · 3 comments
Open

Total size mismatches #4

nikolaydubina opened this issue Mar 9, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@nikolaydubina
Copy link
Owner

No description provided.

@nikolaydubina nikolaydubina added the bug Something isn't working label Mar 9, 2022
@vincentbernat
Copy link

Hey!

I have a 44MB executable. go-binsize-treemap reports 12MB. I have 5.4MB of embedded files. If I link with -s -w, I get a total of 33MB instead. I don't know if the difference is already included into the output of go tool nm -size. If I suppose it is not, I still have 15 MB unaccounted for. If I zero-out one of the embedded file, its size is subtracted from the total, so it does not seem there is a large overhead for embedded files. I am using go 1.18. Any hint where the bytes could be hidden?

@nikolaydubina
Copy link
Owner Author

nikolaydubina commented Jul 22, 2022

Hi, I tried to find missing bytes before too. Even by accounting everything from go tool nm -size there is missing bytes. Some discrepancies can be large.

My best best is to dig into go tool nm -size or Go internals.

Which project you are using? I may try to repro and we can collect where discrepancies coming from together with other reports.

@vincentbernat
Copy link

I am using https://github.com/vincentbernat/akvorado. go tool nm -size doesn't display anything for embedded files. I have spent some time looking left and right without any success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants