Try ktrace. For example: bash$ ktrace Foo This command will execute Foo and create a binary file in the current working directory called ktrace.out. To read the file, just type kdump. This may not be what you're looking for, but it's the first thing I do when I'm tracing a kernel panic. I hope it helps you out. scott On Jul 25, 2004, at 8:22 PM, Scott Judd wrote: Try ktrace. For example: bash$ ktrace Foo This command will execute Foo and create a binary file in the current working directory called ktrace.out. To read the file, just type kdump. This may not be what you're looking for, but it's the first thing I do when I'm tracing a kernel panic. I hope it helps you out. scott On Jul 25, 2004, at 7: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? Matt _______________________________________________ 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. _______________________________________________ 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.