Futher clarification of Kernel source map
Futher clarification of Kernel source map
- Subject: Futher clarification of Kernel source map
- From: Prokash Sinha <email@hidden>
- Date: Wed, 18 May 2016 19:07:27 -0700
Hi All,
I tried the same thing on kernel, kernel.development, kernel.debug.
Also I did set DEBUG=1 ( which did not make much sense, and did not work ).
If I set a break point in any of the hot path ( like, tcp_connect), it
gets hit quite often. But I never see the sources when I go up and down
the frames.
I know for fact, that any kext I built can see the source, well of
course I only tried for debug built).
It would be of real help, if someone tell me what is going wrong.
Basically can I do source level stepping given that I have the correct
build for KernelDebug kit that matches with xnu kernel source.
There are articles on how to have a gdb stub on the VM ( 10.10 osx), but
the host osx does not have gdb. I can build gdb using auto tools on open
source, but not sure if lldb could do this. Furthermore all the articles
shows how to setup and break into the kernel, but not source level stepping.
Not sure if source-map is the right thing or not. On gdb kernel
debugging directory add works all the time.
Prokash
_______________________________________________
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