Re: Project compiles but won't run under xCode 3.0 - class lookup error
Re: Project compiles but won't run under xCode 3.0 - class lookup error
- Subject: Re: Project compiles but won't run under xCode 3.0 - class lookup error
- From: Niels Meersschaert <email@hidden>
- Date: Thu, 24 Aug 2006 10:07:36 -0400
Keep in mind that Xcode 3.0 and all software part of the Leopard
Preview is under NDA. As such, it can't be discussed on a public
mailing list like this.
I realize that can be frustrating, but the NDA allows us early access
to Apple's product pipeline, which is tremendously valuable.
Unfortunately, as has been requested multiple times on this & other
Apple mailing lists, there isn't a separate NDA'd list to discuss
issues with early access products. The only solution (for now) is to
contact ADC thru either the http://developer.apple.com/contact/ form
or to file a bug report using BugReporter.
Good luck,
Niels
On Aug 23, 2006, at 5:22 PM, Matthieu Kopp wrote:
Hi,
We tried to migrate some projects to xCode 3.0 and are experiencing
the same problem every time.
The project compiles and runs fine in xCode 2.3 (GCC 4.0). When
opened in xCode 3.0, the project compiles (after a few changes in
our imports) but does not run.
It crashes with a EXC_BAD_ACCESS in a line like this one:
FooClass *foo = [[FooClass alloc] init];
The stack trace in the debugger indicates that it cannot find some
class. I kind of doubt that it is FooClass.. as the class is
targeted and compiled without problem. It could be a class
referenced by a superclass of FooClass...but it is hard to
tell..;and I cannot interpret the stacktrace.
Is there anything that we should be aware of in 3.0 that has
changed in the way files are compiled and linked ?
Again, this code works fine in 2.3.
We found out, for example, that a wrong declaration like this one:
@class MyNonExistingClass;
referring to a non existing class would not cause any problem in
xCode 2.4...but would prevent the class using that declaration to
be instantiated in xCode 3.0;
We went through all the code and made sure that our import and
@class declaration were correct....but the problem persists.
Is there a a way to find out what is the class that cannot be found
at runtime ... in order to solve the problem?
Thanks in advance,
Matthieu
Aquafadas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to 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