Is there a way I can use the lldb user defined commands, which I can load from a KDK, to determine how much memory my kext has consumed? Is there a way to figure out what size blocks they are? I have already run the showallclasses command and the output has assured me that I am not leaking any objects which are defined by my driver's classes. Thanks, Tim

I am trying to debug a kernel panic in our kext. I can attach to the target Mac over ethernet if I: cause an NMI using add an IOPanic call to my kext and cause it to be executed use Dtrace to invoke a panic However if I reproduce the kernel panic which I am investigating, the Mac just restarts. How can I make the Mac wait for me to attach with lldb rather than restarting? My target configuration is: Mac is 2021 M1 Pro 14" MacBook Pro macOS 14.2 (23C64) Network: Apple Thunderbolt 3 <-> Thunderbolt 3 adapter + Apple Thunderbolt 2 to ethernet adapters Boot-args = "debug=0x44 wdt=-1 kdp_match_name=en8" (I have also tried debug=0x104C0C)

The KDK file for the latest beta of macOS 11.3 does not actually contain a KDK. The file is: "Kernel_Debug_Kit_11.3_Build_20E5224a.dmg" which contains a volume called: "/Volumes/InstallAssistantMAS". The installer on this volume does not actually contain a KDK. I'm just posting here in the hopes that someone at Apple will notice and repost the correct KDK file. Thanks - Tim

We use a custom Mac app and Mac minis in our factories to initialize disks and copy files to them. It would make this process easier, if the person in manufacturing did not have to dismiss the dialog which says "The disk you inserted was not readable by this computer" for each disk. Is there a Finder or system preference I can set to prevent this dialog from being displayed? I know that I can grab the disk using DADiskPeek but one of our tools is a Python script so calling DADiskPeek is not an option. Thanks in advance for your help. Tim

One of the main reasons customers contact our support center is because the wrong version of the driver is loading. This is a direct result of Secure Boot being enabled. How can I detect if Secure Boot is enabled so we can warn users that they will encounter aberrant behavior until they disable it?