Re: compiler bug??
Re: compiler bug??
- Subject: Re: compiler bug??
- From: Cameron Hayne <email@hidden>
- Date: Thu, 8 Sep 2005 15:39:37 -0400
Cameron Hayne wrote:
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.
On 8-Sep-05, at 2:20 PM, Philip Lukidis wrote:
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...
You should add debugging statements to your class and to the clients
of the class to print out:
- sizeof(theObject)
- the offsets of some of the member variables
(e.g. using the XtOffset macro from /usr/include/httpd/ap_config.h
or the equivalent)
This will at least show you which files aren't getting recompiled! :)
--
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