• 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: Size of Binary
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Size of Binary


  • Subject: Re: Size of Binary
  • From: "Kevin Meaney" <email@hidden>
  • Date: Thu, 1 Dec 2005 15:39:40 +0000
  • Organization: Softpress

>On Nov 30, 2005, at 3:19 AM, Kevin Meaney wrote:
>> G'day all,
>>
>> I have been in the process of converting our
>> Codewarrior application to XCode. When building the
>> Mach0 binary in Codewarrior the size of the binary is
>> 14.3 MBytes and the debug symbol file is 22.7 MBytes.
>> When we finally got the application in XCode to
>> compile and link we ended up with a Mach0 binary that
>> is over 900 MBytes in size.
>
>Yes, debug info size is one of the issues we are working on.  In
>Xcode 2.2 you can use the "Essential Symbols" option to reduce the
>size of the binary, and also reduce linkage time.  Note that if you
>do this, you won't be able to give somebody else the debug copy of
>your app (the debug info is left in the .o files...)  But for
>iterative development, that's usually not a big problem.

Do you mean that the debug copy just wont run when given to somebody
else? or they just wont be able to debug the application?

>>
>> When trying to debug the application we get the error:
>> mi_cmd_stack_list_frames: Not enough frames in stack.
>>
>> I recollect reading sometime ago about a limitation in
>> the maximum size of the stack being something like
>> 16MBytes. I was wondering if somehow we have exceeded
>> that limit and the above error message reflects that.
>
>No, these are unrelated issues.  The debugger message has to do with
>our "fast" and "accurate" ways of getting the stack not agreeing in
>some cases.  It has nothing to do with your app.
>
Thanks for that, nice to know. We do find that the debugger appears to be
confused when this happens, but we usually also have a bad access error
message at the same time.

Stripping the symbols reduced the binary size down to 47 MBytes. A lot
more manageable. But of course we don't have the symbols to debug with.

Kevin

 _______________________________________________
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

  • Prev by Date: Re: static / extern fails in GCC 4
  • Next by Date: assigning to variable arguments
  • Previous by thread: Re: static / extern fails in GCC 4
  • Next by thread: assigning to variable arguments
  • Index(es):
    • Date
    • Thread