ReportCrash more a hindrance than a help
ReportCrash more a hindrance than a help
- Subject: ReportCrash more a hindrance than a help
- From: Matt Gough <email@hidden>
- Date: Wed, 23 Jan 2008 14:57:30 +0100
Sometimes my app crashes while its in development (whose doesn't).
I have noticed on many occasions that when this happens the
ReportCrash process can sit there at 100% cpu for several minutes and
my app is still sitting frozen on the screen. During this time, Xcode
won't let me start up another copy and my whole machine can become
unresponsive. I suspect that ReportCrash is trying to gather up a load
of info about the current state of the app.
However I don't see why ReportCrash even needs to get involved when
the app was run from Xcode. Isn't Xcode supposed to drop me into the
debugger with the offending stack.
Anyone else seen this?
Matt Gough
Xcode 3.0 and 10.5.1 BTW
_______________________________________________
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