On 11 Jul 2016, at 15:04, Motti Shneor <[email protected]> wrote: > > I develop a global daemon, maintained by launchd. Obviously It cannot be > distributed in the Mac App Store. To collect crash-reports from customers, I > integrated a mainstream 3rd party crash reporter library (PLCrashReporter). I > collect crashes of our daemon, and send them for analysis, and all is well. > > However, when crash happens, the user can still see a line in the Console > “All Messages” section, and also see the full crash-report in the “System > Diagnostic Reports”. I would want to avoid this, and disable this > crash-reporting that is unusable to me, and exposes private info about my > program (I’m writing a security tool). > > I could not find any process-specific behavior of CrashReporter. The only > thing I could find is how to stop the crash-reporter altogether from > collecting crashes. (see man ReportCrash) - and of course I don’t want this. > > Is it possible at all to stop CrashReporter from collecting just MY crashes? > how? Is there a runtime API (xpc or other) to control CrashReporter behavior? > Any filtering mechanism?
This isn’t really a Cocoa question (you might be better off with the Darwin list), but AFAIK CrashReporter works by connecting to your program’s Mach exception port. Since you’re using it, I’ll note that PLCrashReporter can be set to take over the exception port, but if you look in mach_exception_callback() it forwards crash reports to previously registered handlers, which you probably don’t want. Kind regards, Alastair. -- http://alastairs-place.net _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
