Apple

On Feb 11, 2009, at 5:53 PM, Jean-Daniel Dupas wrote:

....

which is nothing more then what the crash log told me. I was hoping it might give me back a line number, but apparently enough debugging information wasn't available.

Is there a way to make enough debugging information available?

Have a look at this article, it may give you some hints:

http://lapcatsoftware.com/blog/2009/01/20/dsym-in-your-bundle-or-just-happy-to-see-me/

Thanks, but it doesn't say anything that the article from Apple didn't.

*****

btw, the code I wrote to deliberately cause the crash looks like:

char *a = NULL;
char *b = (char*)20;
strcpy( a, "hello" );
strcpy( a, b );
a[10] = docName[4];
CFShow( NULL );

There is clearly more then is necessary, but the reason for that is I was trying to get the optimized build of my application to crash as well. Apparently, the optimizer is to smart for me and it won't crash...I'm guessing because it knows that all of this code is irrelevant and just optimizes it away. Strange how hard it is to get a crash to occur when you want it to, but how easy it is when you don't want it to. :-) In any case, if anyone has a foolproof incantation to trick the optimizer into running code which will deliberately cause a crash, I am interested.

If you want an app that crashes, just do this:

int main(void) {
*(void **)0 = "";
return 0;
}

Thanks, but I want some code that I can insert into the app built with all of the optimizations turned on that will cause it to crash. As I mentioned, the code I posted does not cause a crash in the optimized application when it should, but will cause a crash in the unoptimized application as it should.

References:
	>Using atos & reading crash logs (From: Eric Gorr <email@hidden>)
	>Re: Using atos & reading crash logs (From: Jean-Daniel Dupas <email@hidden>)