3 ms·
Do you know what the underlying problematic instruction sequence is? Or the precise location where it halts?
by metadat 4y ago
Do you know what the underlying problematic instruction sequence is? Or the precise location where it halts?
- alin23 4y agoI have no idea how I could find that, given that the system freezes completely. Maybe tracing the CPU instructions using LLDB might be possible, but the bug is most likely in the kernel code so this would not help much.
- catiopatio 4y agoYou can debug the kernel remotely over Ethernet: https://developer.apple.com/documentation/apple-silicon/debugging-a-custom-kernel-extension https://developer.apple.com/documentation/apple-silicon/debu... If that still fails, virtualization tools provide debugging interfaces you can use to step the execution of the virtualized CPU; e.g. VMware’s “debugStub” feature.
- Firmwarrior 4y agohaha, let's just let the Apple engineers on this thread figure that shit out
- sharikous 4y agoYou can't with Apple Silicon. It's shameful in my opinion. You still can load a core dump or view the state after a NMI but you can't run the kernel under a debugger.
- saagarjha 4y agoYou can, the experience is just not very good.
- bri3d 4y agoThe best public kernel debugger for Apple Silicon is m1n1 from the Asahi project.
- saagarjha 4y agoldr x9, [x8, #0x18]!