Re: Two-machine GDB debugging results in frequent hangs
Re: Two-machine GDB debugging results in frequent hangs
- Subject: Re: Two-machine GDB debugging results in frequent hangs
- From: Joe Lowe <email@hidden>
- Date: Wed, 12 Mar 2014 13:44:25 -0700
When I asked about single-step lockups in kernel debug targets 4 years
ago, there was no feedback from anyone at Apple. The lockups happen.
Others experience them. Maybe noone at Apple single steps in ethernet
GDB kernel debug sessions. I played around with firewire debugging back
when I first experienced this, but gave up for reasons I can no longer
remember. I have gotten used to less when it comes to kernel debugging
on OSX.
http://lists.apple.com/archives/darwin-kernel/2009/Nov/msg00017.html
I would be interested to know if this has been resolved with debugging
10.9 via lldb.
Joe L.
Peter Gibson wrote:
I'm debugging a KEXT on a target system running 10.8.5 from a
host (also running 10.8.5) using gdb over Ethernet. On the target, I've
set the nvram boot-args setting is "debug=0x115 -v pmuflags=1".
However, even with "pmuflags=1", I still see the debugger hang
when I single-step from a breakpoint. This problem happens fairly
frequently and the only resolution I have is to power-cycle the target
and start over.
What could be causing these hangs and what else can I do to keep
them from happening?
Thanks!
_______________________________________________
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