Re: Xcode 2.1 debugger grief
Re: Xcode 2.1 debugger grief
- Subject: Re: Xcode 2.1 debugger grief
- From: Alex Raftis <email@hidden>
- Date: Thu, 9 Jun 2005 08:24:17 -0500
On Jun 8, 2005, at 4:58 PM, Ricky Sharp wrote:
For a particular control/cell I'm debugging, the cell's currentValue
is set to 50. Yet theOldCurrentValue variable above is always is set
to 0. I can step into the cell's currentValue method and verify that
the currentValue ivar is indeed 50.
Finally, I throttled back even further to target 10.3 and to use the
10.3.9 SDK. Debugging then works a-ok. theOldCurrentValue is set to
a value of 50.
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.
Actually, seems like you're hitting an optimization issue. For example,
does your code ever use "theOldCurrentValue"? If it doesn't, Gcc 4.0 is
quite likely not bothering to do the assignment, since the variable
isn't used. But it's also not that simple. Gcc might also be sharing
variable space, and there for doesn't assign to your above variable,
but instead holds the value somewhere else.
The quick way to test this is to compile with no-optimization. If that
fixes your problem, then you know what was doing it to you. If you need
the optimizations, try putting in a print statement to show the value
of the variable. This often causes the compiler to optimize the
variable differently.
Also, don't assume it's your SDK's. The most likely culprit could still
be the compiler. You should be able to switch your compiler to Gcc 3.3
while still using the Tiger frameworks.
Alex Raftis
---
email@hidden
_______________________________________________
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