Re: Debugging kext in lldb. Reading cpu_data_t offset 0x18 using %gs base address.
Re: Debugging kext in lldb. Reading cpu_data_t offset 0x18 using %gs base address.
- Subject: Re: Debugging kext in lldb. Reading cpu_data_t offset 0x18 using %gs base address.
- From: Slava Imameev <email@hidden>
- Date: Mon, 18 Jun 2018 05:49:54 +1000
Hi,
The cpu_preemption_level values were altered by the panic code. The actual
values might be calculated by subtracting 3 from the cpu_preemption_level value
for a CPU that panic'ed (panic_trap_to_debugger, kdp_i386_trap increase it)
and 1 for other CPUs(a value is increased when processing IPI / NMI sent to
freeze CPUs). That said the CPU's preemption level for a cpu that called
msleep() was -1 before calling panic() and 0 for another cpu. The
showcurrentstacks command has a bug by reporting values altered either by
panic() or a kernel debugger code.
_______________________________________________
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