Add -d archs data source for Mach-O universal binaries #481
+351
−0
Conversation
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
Implements the 'archs' data source to break down universal binaries by architecture. This allows users to: - View file size breakdown by architecture: bloaty -d archs - Filter to specific architecture: bloaty -d archs,segments --source-filter=arm64 - Hierarchical breakdown: bloaty -d archs,segments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implements the 'archs' data source to break down universal binaries by architecture.
This allows users to:
This was proposed in #153 (comment) to show the breakdown per architecture using the --source-filter= option.
Note: this has the current limitation which shows incorrect VM sizes because both architectures have overlapping VM addresses, so the workaround would be --source-filter=, or to only use --domain=file. The overlapping VM addresses requires separate address spaces are used. e.g. #480