Missing Kernel Debug Kits for OS X 10.10.2 and Security Update 2015-001 kernels
| Originator: | phil | ||
| Number: | rdar://19846297 | Date Originated: | 16-Feb-2015 |
| Status: | Duplicate of 19892615 (Closed) | Resolved: | |
| Product: | OS X SDK | Product Version: | 10.10.2, 10.9.5, 10.8.5 |
| Classification: | Other | Reproducible: | Always |
Summary: No Kernel Debug Kits are available at http://developer.apple.com/downloads for the operating system kernels included in the following recent OS X system updates: - OS X Update 10.10.2 - Security Update 2015-001 for Mavericks and Mountain Lion This makes it very difficult to debug kexts running on the latest, fully patched versions of these operating systems. Steps to Reproduce: 1. Configure the target system running a fully patched version of OS X Yosemite, Mavericks or Mountain Lion for kernel debugging. 2. Load a kext to debug (e.g. via kextutil) 3. Enter the debugger (via NMI or exception in the kernel) 4. Attempt to connect to the crashed kernel from another system using lldb or gdb with the latest kernel debug kit for the target's OS Expected Results: A symbolicated debugging session, with all kernel debugging macros working. Actual Results: Symbolication in lldb/gdb is nearly impossible due to version mismatch. For example, lldb reports: "warning: Host-side kernel file has Mach-O UUID of 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0 but remote kernel has a UUID of 45486BF2-BDDE-34CB-8C71-606FF3FE181B -- a mismatched kernel file will result in a poor debugger experience." Version: OS X 10.10.2 OS X 10.9.5 with Security Update 2015-001 OS X 10.8.5 with Security Update 2015-001 Notes: Configuration: Attachments:
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
Apple Developer Relations, 24-Feb-2015 09:10 AM
Engineering has determined that your bug report is a duplicate of another issue and will be closed.
The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.