• 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: -gfull + dead cod stripping
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -gfull + dead cod stripping


  • Subject: Re: -gfull + dead cod stripping
  • From: Brad Oliver <email@hidden>
  • Date: Mon, 16 Aug 2004 22:45:01 -0700

My question is, why would dead-stripping inits and terms be dangerous?
(Presumably as the passage says, it only does this to dead inits and
terms....)

I've been bitten by this before. ;-)

Let's say you've got a class that isn't referenced by your app directly. That is, no code calls into methods for this class. If dead-code stripping were on, this class would vanish.

But let's say that this class does something in its constructor to place a pointer to itself into an object table or something similar. Now you've got a situation where your app will call into that class indirectly, but only if the constructor is there to insert the object into your app at runtime.

--
Brad Oliver
email@hidden
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: Linking errors
  • Next by Date: Re: Xcode 1.5 - how to select Find results?
  • Previous by thread: Re: -gfull + dead cod stripping
  • Next by thread: XCode 1.5 debugger not showing variable summaries?
  • Index(es):
    • Date
    • Thread