site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com -- Terry Thanks, Eric _______________________________________________ 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 Mar 9, 2006, at 3:24 PM, Eric Long wrote: So pretty clearly, the AirPort issue is that you are connected, and the default route is through that, rather than through the attached network cable. If you tell it to not use the AirPort by disconnecting/disabling it in software, your problem should go away. There's no need to physically remove the card. I turned off Airport, including disabling it in my port configurations and still had the problem. You need to disable the kext so that the driver didn't load and the hardware is not discovered by the OS. Where can I find instructions to configure for Firewire debugging? There is a document included in the kernel debug kit, as well as a kext to permit debugging over FireWire. If I go the other direction and make the PB the dev machine and the tower the target, I don't see this happen, but when I try to list any sources all I get is a line number and the path to the source. It's completely useless. Any idea why I wouldn't be able to properly list sources going the other way? Yes. You must explicitly symbolicate your kext, and the sources must be in the same relative location. The debugger will tell you what it's trying to list, and this is the path that you must have populated with the KEXT information. Generally, if I'm doing developement on multiple machines, I put the stuff near the root of a volume, and then on the debugging machine, after I copy things over, I create a symbolic link to make sure the same path resolves to the same files there. For symbolication for kext debugging, there's a knowledge base article on kext debugging on developer.apple.com that covers things pretty thoroughly, but here's the gist of it: (1) Get a debugger attached to the machine that has the kext that you want to debug loaded (2) Use the "showallkmods" command to get the load address for the kext (3) Execute the command "kextload -s /tmp -n <my_kext_name.kext>"; it will ask you for the load address (replace "<my_kext_name.kext>" with whatever your kext is) (4) Add the symbol file into the debugger using the "add_symbolfile <symbol_file_name.sym>" (replace "<symbol_file_name.sym>" with the name of the symbol file that was generated by the "kextload" command in step 3) (5) Happy Debugging! This email sent to site_archiver@lists.apple.com