site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com [ ... ] So your options are, in preference order: Not without using one of the previously discussed methods, no. -- Terry _______________________________________________ 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... On Mar 4, 2010, at 12:56 PM, IainS wrote: On 4 Mar 2010, at 20:25, Terry Lambert wrote: (1) Fix whatever underlying problem is resulting in abort() being called. well, in the case of this testsuite code, the abort() is an intentional "output" - it signifies that a particular test/aspect has failed. Realize that thie SA_CORE is mandated by POSIX. So on most UNIX and UNIX-like operating systems, you will, without an overriding setrlimit(), be generating core dumps by calling abort(), which is probably not what you want your test suite doing. (5) Disable Crash Reporter entirely ... in this case, if it's possible to suspend crash reporter (selectively) ... that would be the optimum. ... for the record, (a) how is this achieved? (I'd head for launchd plists .. but that might not be the right place.. ) The procedure has changed between OS versions; since you previously specified "Leopard and later", you should probably consult the ReportCrash man page for the system you want to disable it on. (b) is it possible to disable for one user ... or even for one process ? This email sent to site_archiver@lists.apple.com