Hi, the KDK from Apple includes a README file (.txt or .html, I forget) which
describes how to set up kernel debugging. I'd start by looking at those notes.
There have also been WWDC sessions that talk about kernel debugging, e.g.
https://developer.apple.com/videos/play/wwdc2013/707/
(there a
Ya. I have followed the .html README file for OSX 10.9. It has given the
target path for lldb should be the mach_kernel in KDK.
Now my question is ... As i have put the hard debug point in my kernel
extension, which leads the kernel to go into panic mode and there it is
waiting for debugger to con
Is your kext loaded in lldb when you're connected to the kernel? If you do
'image list' do you see your kext there? Does it show the dSYM, which has all
of the debug information, also loaded for your kext? If your kext with its
dSYM is on the local filesystem, you can add a line to your ~/.ll
Hi,
I m able to do remote kernel debugging but on two physical mac 10.11 El
Capitan. why is it giving me problems on two VMs or 1 physical machine n
one VM ?? Is it necessary to have both physical machines n not VM ??
On Jul 29, 2016 3:34 AM, "Jason Molenda" wrote:
> Is your kext loaded in lldb
Hi,
I m able to do remote kernel debugging but on two physical mac 10.11 El
Capitan. why is it giving me problems on two VMs or 1 physical machine n
one VM ?? Is it necessary to have both physical machines n not VM ??
On Jul 29, 2016 3:34 AM, "Jason Molenda" wrote:
Is your kext loaded in lldb w
Ah, I don't know how to do kernel debugging with macOS running under a VM. I
think this sounds more like a question for the apple devforums, I think it's
more of a "how do I do kext debugging with a VM", not so much an lldb question.
> On Jul 28, 2016, at 7:38 PM, hrishikesh chaudhari
> wrote
https://llvm.org/bugs/show_bug.cgi?id=28709
Ilia changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
