Re: How to interpret library sizes reported by "size"
Re: How to interpret library sizes reported by "size"
- Subject: Re: How to interpret library sizes reported by "size"
- From: David Hoerl <email@hidden>
- Date: Fri, 25 Apr 2014 14:29:56 -0400
On 4/25/14, 2:24 PM, Kyle Sluder wrote:
On Fri, Apr 25, 2014, at 11:14 AM, David Hoerl wrote:
I have an iOS library (.a) and would like to determine the actual size
it will consume when linked into an app (client asked).
So, after a long time poking around trying to find the right tool, I
tripped on "size" (who would ever have guessed that name!):
$ size -arch arm64 myLib.a
__TEXT __DATA __OBJC others dec hex
18436 7156 0 42642 68234 10a8a myLib.a(a.o)
1659 528 0 7209 9396 24b4 myLib.a(b.o)
...
I know what text and data are, but have no clue as to what "others"
means. This is library is a Foundation Objective C library.
Can anyone shed some light on what "others" might be? Its significantly
larger than the "text" segment.
You can get a list of all the sections in a binary by using otool -l.
They'll be listed as part of the LC_SEGMENT or LC_SEGMENT_64 load
command. That'll tell you what sections the "other" column covers. (I'm
not sure knowing that has much use other than personal edification.)
--Kyle Sluder
It looks like much of the "others" is consumed by segments named
"__debug_..." - I'm going to guess if I build this thing stripped much
of that will disappear!
Thanks,
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden