site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com At 12:00 +0530 29/8/05, Karunakar Reddy G wrote: I'd try and get a kernel core dump. <http://developer.apple.com/technotes/tn2004/tn2118.html> Serial debugging requires a real serial port; a USB dongle will not do. The recommended approach is to use two machine gdb over ethernet. -- 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 Aug 30, 2005, at 5:37 AM, Quinn wrote: 3. I have custom usb driver on my Mac OS X 10.4 system, it is going to crash after 30 hours and no display on monitor (Like Backtrace , program counter etc..) during crash. Which is the best debugging method to adopt for this problem? If that fails, things get harder. You have to recompile the kernel with serial debugging (ddb) enabled. Of course, you'll have to run on a machine with built-in serial, which is hard to find these days. There are instructions for this (to my extreme surprise!) in the "Kernel Programming" book on our web site: <http://developer.apple.com/documentation/Darwin/Conceptual/ KernelProgramming/build/chapter_18_section_5.html#//apple_ref/doc/ uid/TP30000905-CH221-CIHDEDFH> The instructions are a little out of date. Specifically, to enable serial console support, you no longer need to change "osfmk/ppc/ serial_console.c". Rather, you can just change the PPC build configuration file "xnu/osfmk/conf/MASTER.ppc" by uncommenting the following line. #options SERIAL_CONSOLE_DEFAULT Apparently, we also ship two machine gdb-over-firewire, according to the readme in "/Developer/Extras/Kernel Debugging/", if you have the developer tools installed on your machine. This email sent to site_archiver@lists.apple.com