On Jul 25, 2004, at 6:34 PM, Shawn Erickson wrote: On Jul 25, 2004, at 5:57 PM, Matt Jaffa wrote: Hi, I have successfully tracked down how to repeat my KEXT causing kernel panics, and I have successfully connected to it remotely to debug, but once I am connected and attached to the remote machine, what must I type/do to figure where in the code was the problem? Not sure someone can help you much via the medium of email, it is a big complex subject... I suggest reviewing what documentation you can find on GDB and any example of using it. Have you looked over the following that Apple provides...? <http://developer.apple.com/documentation/Darwin/Conceptual/ KernelProgramming/build/chapter_18_section_5.html> <http://developer.apple.com/technotes/tn2002/tn2063.html> Oops... I meant to point out the use of the "trace" command in GDB is likely the first step if you have it trapped during a panic in the debugger. If you have symbols for your KEXTs loaded it should quickly point you to the location of the issue. Additionally you can down load the symbols for the kernel you are running [1] to be able to better understand the Apple half of the equation. Also the Apple folks have a set of GDB macros to help debug IOKit, etc. however I cannot recall how to get them at the moment. -Shawn [1] <http://developer.apple.com/sdk/> look for "Kernel Debug Kit" on that page and download the one that matches the OS you have installed. _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.