• 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: Debug Problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debug Problems


  • Subject: Re: Debug Problems
  • From: Chris Espinosa <email@hidden>
  • Date: Sun, 12 Jun 2005 09:36:17 -0700


On Jun 12, 2005, at 9:24 AM, Jesse Grosjean wrote:

Sorry if this has already been mentioned.... but


I've been having lots of trouble making the debugger (in 2.1) work properly and think I've traced it to an incorrect default setting. If you create a new project the "Optimization Level" for the "Debug" configuration is set to "Fastest, Smallest". If you change this to "None" then clean everything debugging seems to work well again.



This is a well-known trait of optimized code in all environments.  A compiler will reorder instructions, take shortcuts, hide variables, and make other assumptions from your code that make it differ wildly from the way you wrote it.  Setting the optimization level to "None" in all Development or Debug build settings or configurations is highly recommended.

Chris
 _______________________________________________
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:
    • Re: Debug Problems
      • From: Justin Greenfield <email@hidden>
References: 
 >Debug Problems (From: Jesse Grosjean <email@hidden>)

  • Prev by Date: Debug Problems
  • Next by Date: Re: Xcode 2.1 debugger grief [Solved]
  • Previous by thread: Debug Problems
  • Next by thread: Re: Debug Problems
  • Index(es):
    • Date
    • Thread