Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I wrote the following code to induce a crash (I was testing out some issues with CrashReporter):
int *nullp = NULL;
int val = *nullp;
NSLog(@"Hello world %d", val);
In a brand new project (I put it in the app delegate’s applicationDidFinishLaunching:) it crashes as expected. But when I add it to one of my existing projects, it doesn’t crash! In fact, it ends up printing “Hello world 0” to the system log.
This doesn’t make any sense to me. Why doesn’t the null dereference cause a crash?
Dereferncing NULL has undefined behavior, it doesn’t have to cause crash.
That being said, if you have different compiler options in the two project you have a good chance to get different behavior for those cases. See this LLVM blog post about undefined behaviors.