site_archiver@lists.apple.com Delivered-To: Darwin-dev@lists.apple.com User-agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Just an untested idea... try kill(getpid(), SIGILL);? On Apr 13, 2009, at 3:14 PM, James Walker wrote: static void AbortHandler( int /* inSignal */ ) { long* badAddr = 0; *badAddr = 7; } -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> _______________________________________________ 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... Kevin Van Vechten wrote: When my app receives SIGABRT, I want to force some kind of crash that will generate a crash report. I tried installing a SIGABRT signal handler like this: On Tiger, it partly works: There is a crash log, but the app keeps running in a hung state. On Leopard, there's just a hang, no crash report. It turns out that on Leopard, I don't need the handler at all, just calling abort() causes the "unexpectedly quit" dialog to appear, and the app to go away. On Tiger, your suggestion is no better or worse than what I had before... the dialog appears, but the app hangs around. This email sent to site_archiver@lists.apple.com