On Jul 27, 2011, at 11:48 AM, Shantonu Sen wrote: There's not an address in the backtrace which resolves to anything at all.
Please be more specific. Addresses in kexts wouldn't be in the static kernel text, obviously.
Obviously.
I'm not talking about kext addresses not resolving. There are always frames in the backtrace which correspond to OS X panic handling code, or to the OS functions that called the kext, or to the call that actually crashed. The crash occurred on 11A511, and in the BT below, with the 11A511 KernelDebugKit, none of the addresses as shown in the BT resolves to a known symbol.
I found that if I prepend 0xffffff8000 to each of the addresses they do resolve to the expected OS functions, so I can do what I need to do. The TN should probably be updated to reflect that, because following the instructions in the current TN won't actually help on a 64-bit system...
Kevin
Wed Jul 27 06:01:53 2011 panic(cpu 1 caller 0x24480e): "zalloc: \"non-kernel map entries\" (7181302 elements) retry fail 3, kfree_nop_count: 0"@/SourceCache/xnu/xnu-1699.22.73/osfmk/kern/zalloc.c:1677 Backtrace (CPU 1), Frame : Return Address (4 potential args on stack) 0x112bd48 : 0x22032e (0x6abf4c 0x112bd68 0x229ef0 0x0) 0x112bd78 : 0x24480e (0x6ae698 0x6b02af 0x6d93f6 0x3) 0x112bdf8 : 0x245069 (0x285086c 0x1 0x112be88 0x27e164) 0x112be08 : 0x27e164 (0x285086c 0x1ed2e038 0x1ed2e000 0x1000) 0x112be88 : 0x23837c (0x6a8f4e0 0x6b183bc 0x112beb8 0x5bc9a6) 0x112beb8 : 0x5645bf (0x86597c0 0x1 0x4 0x112bed8) 0x112bee8 : 0x5646e9 (0x86597c0 0x6ace358 0x1 0x4) 0x112bf18 : 0x564b06 (0x86597c0 0x6a392b8 0x1 0x1) 0x112bf48 : 0x564c4d (0x6a392b8 0x112bf68 0x0 0x0) 0x112bf78 : 0x5f015a (0x6a392b8 0x6b4a614 0x7001a98 0x6b4a610) 0x112bfc8 : 0x2e3977 (0x6b4a610 0x0 0x10 0x6b4a610)
|