Re: Hello Debugger/Goodbye Machine
Re: Hello Debugger/Goodbye Machine
- Subject: Re: Hello Debugger/Goodbye Machine
- From: Derek Kumar <email@hidden>
- Date: Tue, 14 Mar 2006 16:24:54 -0500
After some investigation, it appears that forcing the PMU driver (on
portables like the PB G4 which are PMU-based) to operate in polled
mode by adding the "pmuflags=1" boot-arg will bypass one possible
cause of shutdowns while debugging (when breakpoints cause kernel
debugger entry in the middle of a PMU transaction, causing the PMU
watchdog to trigger on timeout). The correlation, if any, with the
presence of the Airport card is unclear.
Hope that helps,
Derek
P.S.: Also, from your description, it appears that you're seeing a
spurious "breakpoint" entry, perhaps because the "NMI" button press
isn't being adequately de-bounced. Feel free to add to the
information in radar 4473217 (with a backtrace from the spurious
breakpoint) if you continue seeing that with the pmuflags boot-arg.
On Mar 9, 2006, at 3:14 PM, Eric Long wrote:
I'm wondering if anyone has seen the kind of problems I am
experiencing
debugging my kext with gdb.
My two machines are a 15" 1.5GHz G4 PB and a Dual 2Ghz G5 Tower. Both
running 10.4.5. Both with the Xcode 2.2.1 dev tools.
I'm following the same basic process for debugging as the Hello
Debugger
example:
http://developer.apple.com/documentation/Darwin/Conceptual/
KEXTConcept/KEXT
ConceptDebugger/hello_debugger.html
If I attempt to make the PB the target and the Tower the dev
machine, at the
point in gdb when I enter "continue" I immediately get a message in
the
Terminal that says:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00095dec in Debugger ()
And the PB immediately shut down! Huh?
I haven't set any breakpoints nor does my kext have any code to
drop into
the debugger. Just selecting continue after attaching shouldn't
get tangled
with my kext as far as I know, so I don't what is dropping into the
debugger
or causing the machine to shut down.
This is pretty much a fresh system on the PB. The only third party
extension besides mine installed is Cisco VPN extension.
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.
I've ensured the sources on both machines are in sync, if that has any
bearing. I don't know what gives here.
The last time I did kext debugging was under Panther. I didn't have
problems
like this.
Any ideas?
Thanks in advance,
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