Re: Darwin-kernel Digest, Vol 3, Issue 24
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Feb 1, 2006, at 11:13 AM, Jason Seng wrote: Hi Derek, Peter, Also, it's possible to do both crashdumps and kernel debugging over a firewire transport, which can be pretty useful in some cases. I'll check to see if those tools can/have been made available externally. Cheers, -- J-Sun Seng Derek _______________________________________________ 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... Yes they are. Look in /Developer/Extras/Kernel Debugging for the bits needed to enable gdb over FireWire. Another interesting tool is FWMemView in the FireWire SDK. This tool allows you to view (and manipulate!) the physical memory of a running system connected by FireWire. That's great to hear, thanks. I don't, however, see "FireWireCoreDumper" (a crashdump server that listens on firewire) or the gdb plugin which bypasses the KDP protocol (so it doesn't need an active processor, as is the case when you can't force the machine into the debugger - useful in certain pathological situations where processors are spinning with interrupts off, or the processor has entered a state such as checkstop) and performs a hashtable walk manually, so that you can look at virtual addresses (since Firewire DMA, of course, operates in physical mode). It would be good if we can get those out, although the latter is probably not particularly useful externally. This email sent to site_archiver@lists.apple.com
participants (1)
-
Derek Kumar