site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On 19-Dec-07, at 00:30 , James Peach wrote: This works, but re-raising a signal does run the risk of producing a stack trace that CrashReporter can't walk correctly. I've seen cases where my own stack logging code and CrashReporter disagree wildly on what the real stack trace is. IMHO it's better to just let the fatal signals go straight through to CrashReporter unless you have a really food reason. Is there any way for a developer to find out crashes related to their software via Apple? It would be ideal if there was service that I could sign up to as a developer or if MacOS X could send the log to the the application developer, though I realise the latter might be considered a 'security risk'. Andre _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com