Re: Resolving EXC_BAD_INSTRUCTION (Where do I begin?)
Re: Resolving EXC_BAD_INSTRUCTION (Where do I begin?)
- Subject: Re: Resolving EXC_BAD_INSTRUCTION (Where do I begin?)
- From: Paul Walmsley <email@hidden>
- Date: Wed, 06 Sep 2006 17:38:59 +0100
Just because the code worked correctly under CodeWarrior doesn't mean
it was written correctly. Turn on compiler warnings; turn off
optimizations; use the debugger. It shouldn't be too hard to find. ;)
I often find one of the most likely causes of errors when switching from
one compiler to another is static initialisers. If you have static data
in one .cpp file that references static data in another then that's one
of the first places your program will blow up. C++ makes no guarantee
of the order of initialisation, and the compiler won't warn you about it
either.
However, in this case, you'll still be able to see where it's going
wrong in the debugger.
Paul
_______________________________________________
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