Options for receiving Mac crash reports for my application (from client machines)

I am writing an application for Mac OS X (> = 10.8). This is not an appstore app. I would like to make the process of sending crash reports as simple as possible for my clients. I found a lot of threads on this, but most of them are pretty old, so I would like to double-check the state of this.

1) Is it true that CrashReporter does not allow overriding the load path for failure?

2) Is it true that third parties do not have access to crash reports for their applications when these reports are uploaded to Apple?

3) Can I get CrashReporter to build a crash report without displaying the user interface? This restriction without a UI should only apply to my application ... I do not want to change the global Settings. I need to do this from the code of my applications (I can not ask the client to change the conf file). Then I could let the reporter generate the file and then display my user interface (either immediately or the next time the application is launched, maybe)

4) Can I get CrashReporter to show my interface, not the built-in one? It seems unlikely, but I thought.

5) Can I use the code that generates the crash report in CrashReporter as the lib that I refer to and run my own expression? I do not mind their report format, and since I assume their library will always work with OS versions, it seems that it would be great.

6) What applications use third-party applications? I saw links to BreakPad, but I'm a little nervous about this process. I saw a couple of other libraries, but no one has for many years, which made me nervous.

+4
source share

All Articles