On Friday, January 4, 2002, at 06:21 AM, Andrew Gallatin wrote: Umesh Vaishamapayan writes: Thanks for the feedback. Fortunately you are not the only one who does not like the current panic UI [I wonder why? :-)] So there is already Radar tracking the issue of improving the panic UI. Speaking of the panic UI .. As a new Darwin driver developer coming from a FreeBSD (and Tru64) background, I've found it incredibly painful to analyze a panic with only one Darwin system. Are there any plans to implement either crashdumps for post-mortem debugging Crashdump like FreeBSD are not possible in Darwin because there is no swap partition to dup to. We swap to the file system, and in case of a panic/crash you do not want to write to your file system. You might want to check Darwin-developer list archives. This has been discussed at length in the past. or at least optionally expose a console interface to ddb so that one can get a symbolic stack trace (like you can with the ddb in *BSD & Tru64)? Well, if you build and run DEBUG kernel, you get ddb... --Umesh