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

Re: debugger problems


  • Subject: Re: debugger problems
  • From: Alexander von Below <email@hidden>
  • Date: Sun, 14 Oct 2007 15:22:26 +0200

Never ever use optimization for debug code, unless absolutely necessary. Todays optimizers will render your code unreadable.

The second thing to do would have been to either analyze the assembly code, or to go old-school and use command line gdb

Alex

Am 14.10.2007 um 15:15 schrieb H M:


On 14. Oct 2007, at 12:54, Alexander von Below wrote:

First thing to do: Check if all code optimizations are disabled for debug builds

Alex

I changed a couple of things. one option was set to fastest, now it's set to none, another was set to G4, and I changed that too. those changes had 2 effects: the resulting files are much bigger than before, and the debugger seems to work again.


just FMI: what would have been the second thing to do?

_______________________________________________ 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
References: 
 >debugger problems (From: H M <email@hidden>)
 >Re: debugger problems (From: Alexander von Below <email@hidden>)

  • Prev by Date: Re: debugger problems
  • Next by Date: Re: GCC 3.3 template compile error?
  • Previous by thread: Re: debugger problems
  • Next by thread: Re: debugger problems
  • Index(es):
    • Date
    • Thread