site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com <http://developer.apple.com/technotes/tn2004/tn2118.html> -- Terry _______________________________________________ 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... On Dec 15, 2006, at 9:20 AM, Quinn wrote: At 20:24 -0700 13/12/06, Joseph Oreste Bruni wrote: On my test system, I can start and kill my process all day long and never reproduce this. In production, where the system runs for weeks, the condition occurs... You might want to set up kernel core dumps on your production machine. When you get a stuck process, you can press NMI to dump a kernel core. From that you could look at the state of the stuck process. I concur; I meant to respond to this earlier, and my opinion is that there's nothing for this except the kernel debugger. If you have a second machine to debug with, then that wold be better thn a core dump server (unless there was an intent to send the core to Apple in a bug report), since a lot of the kgmacros that would be useful for debugging this issue do not work on core files because of gdb limitations that have not been addresses (specifically local shadow register state being used in place of image register state so things like "switchtoact" actually switch). This email sent to site_archiver@lists.apple.com