Re: Hello Debugger/Goodbye Machine
Re: Hello Debugger/Goodbye Machine
- Subject: Re: Hello Debugger/Goodbye Machine
- From: Derek Kumar <email@hidden>
- Date: Thu, 9 Mar 2006 19:20:00 -0500
I've sent a note to the Airport driver maintainer about this--I
haven't personally seen the shutdown-after-continue behavior; it may
be tied to some specific combination of driver/firmware/system. It's
possible that disabling interrupts for an extended period of time (as
with the debugger) triggers some sort of anomalous interaction with
Airport. Please file a bug as well...
Apropos Terry's comment:
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.
This isn't the case...the debugger is "passive" in the sense that it
doesn't initiate connections in the two-machine debugging scenario;it
responds to incoming gdb packets (and swaps sources and destinations
at each protocol layer), and doesn't attempt to route packets and so
on. Also, the kernel debugger does use a polled mode driver, but the
only polled mode implementations that register with the debugger are
the ethernet drivers. Typically, the debugger is bound to the "built-
in" en0 interface, unless you specify the "kdp_match_name=en?" boot-arg.
Terry's suggestion of disabling the airport driver rather than
resorting to physically removing the card is a definitely worth a try
(by moving /System/Library/Extensions/AppleAirport* aside, or
kextunload-ing it, for instance).
Derek
On Mar 9, 2006, at 6: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.
Where can I find instructions to configure for Firewire debugging?
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?
Thanks,
Eric
_______________________________________________
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
_______________________________________________
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