Re: Using atos & reading crash logs
Re: Using atos & reading crash logs
- Subject: Re: Using atos & reading crash logs
- From: Jean-Daniel Dupas <email@hidden>
- Date: Wed, 11 Feb 2009 23:53:22 +0100
....
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:
*****
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; }
|
_______________________________________________
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