site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com kr = task_set_exception_ports( mach_task_self(), EXC_MASK_ALL, MACH_PORT_NULL, EXCEPTION_DEFAULT, 0 ); S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 11:12 +0200 3/10/07, Jonas Maebe wrote: I have crashreporterd disabled on my machine, because I regularly run (test) programs which trigger hardware exceptions but catch them and deal with them via Unix signals (and crashreporterd nevertheless insists on dumping crash logs in such situations because it can't know those exceptions are caught at the BSD level, which is pretty annoying even if it's set not to display dialog boxes). I don't know how to solve your panic log question, but I have an alternative approach that might help you avoid this problem in the future. Rather than disabling crash reporter globally, disable it for the test programs. If you add the following line to main, crash reporter won't hear about any crashes. This email sent to site_archiver@lists.apple.com