RE: compiler bug??
RE: compiler bug??
- Subject: RE: compiler bug??
- From: Philip Lukidis <email@hidden>
- Date: Thu, 8 Sep 2005 14:20:56 -0400
You're right, apologies to Chris. But I did try it earlier, with no
success. The symbol is being defined in the GCC settings of the project, so
all source files should see it. And I've done a full rebuild for this
project (there are no other clients).
I'm going to put more padding in various areas in the class to see if
they've been stomped on. Hopefully there is support in gdb for breaking on
memory write...
Philip Lukidis
-----Original Message-----
From: Cameron Hayne [mailto:email@hidden]
Sent: Thursday, September 08, 2005 2:08 PM
To: Xcode Users
Cc: Philip Lukidis
Subject: Re: compiler bug??
Chris Espinosa wrote:
>> This implies that there is some client of the public interface of
>> class
>> that isn't getting recompiled and re-linked when you change the
>> class'
>> formal definition. It's then using invalid offsets into the class at
>> runtime, and "all hell" would indeed break loose.
>>
On 8-Sep-05, at 11:07 AM, Philip Lukidis wrote:
> I've done that. And if that were the case (assuming I understand your
> point), moving the member to another location after the issue has
> occurred
> would not "solve" the issue.
>
Moving the member to a different location would mean that only access
to those member variables after that location would be affected. I.e.
the offsets of earlier member variables would not be affected by the
presence of the ifdef'd variable.
Thus your experience is still consistent with Chris' theory. Check
again that all clients of the class are getting recompiled with the
correct #define's.
--
Cameron Hayne
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