• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to interpret library sizes reported by "size"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to interpret library sizes reported by "size"


  • Subject: Re: How to interpret library sizes reported by "size"
  • From: Kyle Sluder <email@hidden>
  • Date: Fri, 25 Apr 2014 11:24:05 -0700

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
 _______________________________________________
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


  • Follow-Ups:
    • [SOLVED]: How to interpret library sizes reported by "size"
      • From: David Hoerl <email@hidden>
    • Re: How to interpret library sizes reported by "size"
      • From: David Hoerl <email@hidden>
References: 
 >How to interpret library sizes reported by "size" (From: David Hoerl <email@hidden>)

  • Prev by Date: How to interpret library sizes reported by "size"
  • Next by Date: Re: How to interpret library sizes reported by "size"
  • Previous by thread: How to interpret library sizes reported by "size"
  • Next by thread: Re: How to interpret library sizes reported by "size"
  • Index(es):
    • Date
    • Thread