精通Apple调试与逆向工程:LLDB与Python脚本实战

5星 · 超过95%的资源 需积分: 31 12 下载量 117 浏览量 更新于2024-07-19 收藏 64.77MB PDF 举报
"《Advanced Apple Debugging & Reverse Engineering v2.0》是针对苹果平台的高级调试与逆向工程的教程,适用于熟悉Swift或Objective-C的中级到高级开发者,旨在提升他们的调试技能。该资源包括完整高清版内容,并且已更新以支持Xcode 9和Swift 4.0。由于文件大小限制,源代码需在指定链接下载。" 在《Advanced Apple Debugging & Reverse Engineering》中,作者Derek Selander深入介绍了如何充分利用Apple的软件调试器LLDB,揭示了如何通过其广泛的子命令和选项获取程序中的更多信息。书中涵盖了以下几个核心知识点: 1. LLDB高级成就:读者将学习如何掌握LLDB,理解其丰富的命令和选项,从而成为LLDB的专家。 2. 二进制基础:探讨低级组件,如汇编调用约定和动态加载框架的探索,帮助提取程序中的有用信息,深入了解程序运行的底层机制。 3. Python的力量:利用LLDB的Python模块创建自定义调试命令,增强对现有程序的内省和修改能力,提升调试效率和深度。 4. 没有什么是秘密:介绍如何使用DTrace动态追踪框架,编写D脚本来查询macOS系统上的任何感兴趣的信息,实现对系统行为的深入洞察。 5. 案例研究:通过真实的案例,快速定位并解决iOS和macOS开发者在日常开发中常见的问题,提供实战经验。 此书不仅是提升个人技能的宝贵资源,也是解决实际开发问题的实用指南。通过学习,开发者不仅能更快地找到bug,还能了解其他开发者如何解决类似问题,从而提升自己的编程技巧和解决问题的能力。 注意,本书的所有权利由Razeware LLC所有,未经书面许可,不得复制或分发任何部分。同时,书中提供的所有内容(包括源代码)均按照“原样”提供,不提供任何明示或暗示的保证。作者和版权所有者不对因使用本书内容导致的任何索赔、损害或其他责任负责。 书中还特别提到了所有的商标和注册商标归各自所有者所有。此外,作者Derek Selander向他的妻子Brittany表达了感谢,感谢她在作者学习过程中给予的支持和鼓励。 《Advanced Apple Debugging & Reverse Engineering》是苹果开发者提升自身技能,尤其是调试和逆向工程技能的不可或缺的参考资料。通过深入学习,开发者可以掌握更高级的调试技术,提高代码质量和开发效率。
2018-04-04 上传
Advanced Apple Debugging & Reverse Engineering v0.9.5 Explore code through LLDB, Python and DTrace, to discover more about any program than you ever thought possible. Table of Contents 1. Getting Started In this chapter, you’re going to get acquainted with LLDB and investigate the process of introspecting and debugging a program. You’ll start off by introspecting a program you didn’t even write — Xcode! 2. Help & Apropos Just like any respectable developer tool, LLDB ships with a healthy amount of documentation. Knowing how to navigate through this documentation — including some of the more obscure command flags — is essential to mastering LLDB. 3. Attaching with LLDB Now that you’ve learned about the two most essential commands, help and apropos, it’s time to investigate how LLDB attaches itself to processes. You’ll learn all the different ways you can attach LLDB to processes using various options, as well as what happens behind the scenes when attaching to processes. 4. Stopping in Code Whether you’re using Swift, Objective-C, C++, C, or an entirely different language in your technology stack, you’ll need to learn how to create breakpoints. It’s easy to click on the side panel in Xcode to create a breakpoint using the GUI, but the LLDB console can give you much more control over breakpoints. 5. Expression Now that you’ve learned how to set breakpoints so the debugger will stop in your code, it’s time to get useful information out of whatever software you’re debugging. In this chapter you’ll learn about the expression command, which allows you to execute arbitrary code in the debugger. 6. Thread, Frame & Stepping Around You’ve learned how to create breakpoints, how to print and modify values, as well as how to execute code while paused in the debugger. But so far you’ve been left high and dry on how to move around in the debugger and inspect data beyond the immediate. In this chapter, you’ll learn how to move the debugger in and out of functions while LLDB is currently paused. 7. Image it’s time to explore one of the best tools for finding code of interest through the powers of LLDB. In this chapter, you’ll take a deep dive into the image command. 8. Persisting & Customizing Commands In this chapter, you’ll learn how to persist these choices through the .lldbinit file. By persisting your choices and making convenience commands for yourself, your debugging sessions will run much more smoothly and efficiently. This is also an important concept because from here on out, you’ll use the .lldbinit file on a regular basis. 9. Regex Commands In the previous chapter, you learned about the command alias command as well as how to persist commands through the lldbinit file. Unfortunately, command alias has some limitations. The LLDB command command regex acts much like command alias, except you can provide a regular expression for input which will be parsed and applied to the action part of the command. 10. Assembly Register Calling Convention Now you’ve gained a basic understanding of how to maneuver around the debugger, it’s time to take a step down the executable Jenga tower and explore the 1s and 0s that make up your source code. This section will focus on the low-level aspects of debugging. 11. Assembly & Memory In this chapter, you’ll explore how a program executes. You’ll look at a special register used to tell the processor where it should read the next instruction from, as well as how different sizes and groupings of memory can produce very different results. 12. Assembly and the Stack What does being "passed on the stack" mean exactly? It’s time to take a deeper dive into what happens when a function is called from an assembly standpoint by exploring some “stack related” registers as well as the contents in the stack. 13. Hello, Ptrace As alluded to in the introduction to this book, debugging is not entirely about just fixing stuff. Debugging is the process of gaining a better understanding of what’s happening behind the scenes. In this chapter, you’ll explore the foundation of debugging, namely, a system call responsible for a process attaching itself to another process: ptrace. 14. Dynamic Frameworks With dynamic frameworks comes a very interesting aspect of learning, debugging, and reverse engineering. Since you have the ability to load the framework at runtime, you can use LLDB to explore and execute code at runtime, which is great for spelunking in both public and private frameworks. 15. Hooking & Executing Code with dlopen & dlsym It’s time to learn about the complementary skills of developing with these frameworks. In this chapter, you’re going to learn about methods and strategies to “hook” into Swift and C code as well as execute methods you wouldn’t normally have access to. 16. Exploring and Method Swizzling Objective-C Frameworks You’ll cap off this round of dynamic framework exploration by digging into Objective-C frameworks using the Objective-C runtime to hook and execute methods of interest. 17. Hello Script Bridging Next up in the tradeoff between convenience and complexity is LLDB’s script bridging. With script bridging, you can do nearly anything you like. Script bridging is a Python interface LLDB uses to help extend the debugger to accomplish your wildest debugging dreams. 18. Debugging Script Bridging You need a methodical way to figure out what went wrong in your LLDB script so you don’t pull your hair out. In this chapter, you’ll explore how to inspect your LLDB Python scripts using the Python pdb module, which is used for debugging Python scripts. 19. Script Bridging Classes and Hierarchy You’ve learned the essentials of working with LLDB’s Python module, as well as how to correct any errors using Python’s PDB debugging module. Now you’ll explore the main players within the lldb Python module for a good overview of the main parts. In this chapter, you’ll add some arguments to this script and deal with some annoying edge cases, such handling commands differently between Objective-C and Swift. 20. Script Bridging with Options & Arguments When you’re creating a custom debugging command, you’ll often want to slightly tweak functionality based upon options or arguments supplied to your command. A custom LLDB command that can do a job only one way is a boring one-trick pony. In this chapter, you’ll explore how to pass optional parameters (aka options) as well as arguments (parameters which are expected) to your custom command to alter functionality or logic in your custom LLDB scripts. 21. Script Bridging with SBValue & Memory So far, when evaluating JIT code (i.e. Objective-C, Swift, C, etc. code that’s executed through your Python script), you’ve used a small set of APIs to evaluate the code. It’s time to talk about a new class in the lldb Python module, SBValue, and how it can simplify the parsing of JIT code output. 22. SB Examples, Improved Lookup For the rest of the chapters in this section, you'll focus on Python scripts. As alluded to in the previous chapter, the image lookup -rn command is on its way out. When you finish this chapter, you’ll have a new script named "lookup" which queries in a much cleaner way. 23. SB Examples, Resymbolicating a Stripped ObjC Binary When LLDB comes up against a stripped executable (an executable devoid of DWARF debugging information), LLDB won’t have the symbol information to give you the stack trace. Instead, LLDB will generate a synthetic name for a method it recognizes as a method, but doesn’t know what to call it. In this chapter, you’ll build an LLDB script that will resymbolicate stripped Objective-C functions in a stack trace. 24. SB Examples, Malloc Logging For the final chapter in this section, you’ll go through the same steps I myself took to understand how the MallocStackLogging environment variable is used to get the stack trace when an object is created. From there, you’ll create a custom LLDB command which gives you the stack trace of when an object was allocated or deallocated in memory — even after the stack trace is long gone from the debugger. 25. Hello, DTrace You’ll explore a very small section of what DTrace is capable of doing by tracing Objective-C code in already compiled applications. Using DTrace to observe iOS frameworks (like UIKit) can give you an incredible insight into how the authors designed their code. 26. Intermediate DTrace This chapter will act as a grab-bag of more DTrace fundamentals, destructive actions (yay!), as well as how to use DTrace with Swift. In this chapter, you'll learn additional ways DTrace can profile code, as well as how to augment existing code without laying a finger on the actual executable itself. 27. DTrace vs objc_msgSend In this chapter, you'll use DTrace to hook objc_msgSend's entry probe and pull out the class name along with the Objective-C selector for that class. By the end of this chapter, you'll have LLDB generating a DTrace script which only generates tracing info for code implemented within the main executable that calls objc_msgSend.