site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 Joe On 2019-05-16 14:19, Prokash Sinha wrote: Hi All, I do kernel debugging using lldb and target being a fusion VM. It will sincerely help me save lots of annoying time. This, IMO is not a true sense kernel debugger… TIA, -p _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/joe.lowe%40pismotechni... This email sent to joe.lowe@pismotechnic.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com In my experience: The mac kernel intermittently locks up during single-step kernel debugging. This has been an issue since well before 10.12, at least going back to 10.6 . Using breakpoints instead of single-step mostly avoids the kernel debugger lock-ups, but still happens occasionally. For issues where breakpoints don't cut it, things can be pretty frustrating. When step thru the kext code, say for example the _start code, after few seconds, … kernel stopped messages I get. I was wondering if there is any additional param I need to put into my existing param — boot-args-v debug=0x146 pmuflags=1 watchdog=0 kcsuffix=development kext-dev-mode=1