Re: Xcode 2.1 debugger grief
Re: Xcode 2.1 debugger grief
- Subject: Re: Xcode 2.1 debugger grief
- From: Ricky Sharp <email@hidden>
- Date: Wed, 8 Jun 2005 21:27:02 -0500
On Jun 8, 2005, at 7:36 PM, Chris Espinosa wrote:
On Jun 8, 2005, at 4:02 PM, Ricky Sharp wrote:
I have a feeling that both my 10.4.0 and 10.4u SDKs are totally
hosed.
Has anyone else seen strange things with those SDKs? Later
tonight I'm going to do a fresh install of Xcode 2.1. I had
Xcode 2.0 on my box and upgraded to 2.1. I had specified a
custom install so as to include the new SDKs.
I uninstalled version 2.1 and did a clean install. Still have the
same problem. I guess the only thing I can try now is to create a
brand new project and re-add my source, resources etc and hope for
the best.
BTW, the uninstall perl script included with 2.1 doesn't seem to
remove the 10.4 universal SDK. I had to manually delete its .pkg
from /Library/Receipts
SDKs contain no code. They just have header files and stub
libraries with symbols that correspond to the entry points in the
real system. It's very, very unlikely that using an SDK could
result in the changes you described.
You didn't say what you upgraded *from*. If you came from gcc3.3
to gcc4.0, or from Panther to Tiger, there are underlying OS and
compiler changes that might explain this.
A bit back I did a complete clean install of Mac OS X 10.4.0 along
with Xcode 2.0. At that time, I upgraded my Xcode projects to ensure
they would compile with gcc 4.0. That worked a-ok. However, the
target OS was still set to 10.3.
I then did what I described above in moving to Xcode 2.1
You didn't say whether you cleaned your project before building.
If you had libraries lying around that were built in a different
way than the new build, there may be interesting interactions. Do
a full clean before building.
Always did a clean build after changing any of the settings.
As usual, if optimization is on, the debugger will appear to lie to
you. Turn optimization off when debugging.
That's the first thing I checked. optimization is fully off. I also
compared a brand new project's settings to mine just to ensure that
no strange settings were in there. All looked a-ok.
I can switch between the 10.3.9 and 10.4u SDK and can get the problem
to come and go.
I have, however, created a fresh project (minimal Cocoa app) and then
added some simple code (couple classes, getters, setters). I set the
project to target 10.4 and to use the 10.4u SDK. Debugger works a-ok.
I'm now going to start with a fresh Cocoa app and slowly add my
sources in there. Hopefully something will either turn up in my
source, or if everything then works OK, perhaps my project is somehow
corrupt.
Other final details...
Project only contains .m files (everything is Obj-C)
The app needs to link against the Carbon framework (for the single
API SetSystemUIMode). I removed that call and the framework but the
problem still existed.
_______________________________________________
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