Re: Hello Debugger/Goodbye Machine
Re: Hello Debugger/Goodbye Machine
- Subject: Re: Hello Debugger/Goodbye Machine
- From: Terry Lambert <email@hidden>
- Date: Thu, 9 Mar 2006 15:12:22 -0800
On Mar 9, 2006, at 2:00 PM, Eric Long wrote:
I have had the EXACT same problem (on a 1Ghz AI PowerBook) since
Tiger shipped. A few days ago I think I figured out the problem (I've
had access to another machine for debugging, so it wasn't a
priority). I found that if I removed the Airport card, no more auto-
shutdowns when the attach the debugger. No problems for the past few
days.
What gets me is that this problem even exists. There has to be a few
Apple devs debugging on PowerBooks with Airport cards installed.
Thanks for the info.
Considering Airport is built-in on this PB, that's more than a tad
inconvenient!
Derek may want to comment, but...
The remote debugging over the network uses a polled network driver
over the default route for the machine in order to communicate with
the debugging machine. 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.
Alternately, you can configure for FireWire debugging, and use a
FireWire cable between the machines instead. This is generally better
for problems that happen very early in the life of the system anyway,
unless you are building your own kernel and uncommenting the delay and
debugger entry in bsd/kern/bsd_init.c.
-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden