site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com No. Incorrect. -- 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 Apr 10, 2010, at 9:26 AM, William Kucharski <kucharsk@mac.com> wrote: On Apr 10, 2010, at 10:08 AM, Adam Mitchell wrote: I work with Solaris mostly, and when you get a kernel panic you get a memory dump to disk. Does/can OS X do this, too? Unfortunately, the debugging bits of Mac OS X are rather poorly developed compared to Solaris, Solaris dumps to the dedicated swap partition, which Mac OS X doesn't have. I think it would be better to say that the swap management bits of Solaris are rather poorly developed compared to Mac OS X. 8-). All joking aside, dynamic swap sizing is generally more useful than kernel core dumps to local disk, so it's a reasonable design tradeoff for all but .001% of people. with no kernel crash dumps You can dump to pretty much any other machine you have on your network. To look at the dump, you're going to want to use a kernel debug kit and your KEXT sources which are sitting on the crashed machine anyway, so if you can't do live two machine debugging, you have to reboot anyway. and no self-hosted debugging You can operate on a network share containing the dump after the reboot, per above. You can also set the boot arg to enable the kmem device and do read- only, no single-step, no break-point, self-hosted debugging (i.e. look around but not poke around).. You can also use VMWare on Mac OS X server with their special polled mode virtual network driver to loopback debug a VMWare image kernel panic on the machine that's the VMWare host (kernel development to go, on a single MacBook Pro). This email sent to site_archiver@lists.apple.com