Re: Xcode debugging UI question
Re: Xcode debugging UI question
- Subject: Re: Xcode debugging UI question
- From: Chris Friesen <email@hidden>
- Date: Wed, 3 Aug 2005 10:46:24 -0700
On Aug 2, 2005, at 11:20 AM, Bill Monk wrote:
So personally, I think Xcode's current behaviour (not inferring anything from the name of the build style/configuration) is correct.
Surely you don't mean this. If so, you may as well argue that Undo menu items should never be disabled, or that iTunes' "Play" button should remain active when an empty playlist is selected.
So if the song is just silence then you don't want iTunes to play it? That is a better comparison since Xcode doesn't let you debug a file that isn't there...
There are uses for running code in the debugger that does not have symbols. You can even load symbols for that code if you have a build with symbols squirreled away. (At the gdb prompt in the debugger Console: 'help sharedlibrary specify-symbol-file', usage is: 'sharedlibrary specify-symbol-file <shlib num> <path to symbol version>'. The <shlib num> can be found using 'info shared' at the gdb prompt.)
Some developers build their release build, ie optimized, with symbols but ship a stripped copy to customers. (see the man page for 'strip'). This lets them debug the shipped product and the custom doesn't have access to the debugging symbols. Having this symbol version around with executable code matches what the custom is running lets you take a crash trace that just had addresses and map them to locations in your code. (see the man page for 'atos').
Cheers, ChrisF
|
_______________________________________________
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