|
You are here |
www.emergetools.com | ||
| | | | |
jborza.com
|
|
| | | | | You've written an emulator, how do you debug anything running inside? In this post I'll try to describe what I did (and thought of doing), starting from the most crude methods. Using the IDE and debug the emulator binary Here you can read the program state using just the IDE debugging facilities. Hopefully the code being debugged is simple enough that you can just correlate the (hopefully assembly) source listing to the disassembled instruction and view the machine state. | |
| | | | |
knight.sc
|
|
| | | | | When reverse engineering macOS binaries that are written in Objective-C, class-dump is a common tool used to extract Objective-C declarations from the runtime information stored in the Mach-O files. With Swift binaries, since there is Objective-C compatability, sometimes you can extract declarations using class-dump but not always. Swift has a rich set of type metadata itself but the documentation is not up to date. With Swift 5 bringing ABI stability I thought it would be interesting to take a look at the type of metadata availble in Swift binaries. | |
| | | | |
swiftrocks.com
|
|
| | | | | StaticString is an interesting type in Swift. Let's see how it works! | |
| | | | |
bernsteinbear.com
|
|
| | | [AI summary] This blog post compiles extensive resources for learning and developing programming languages, including compilers, runtimes, optimization techniques, and related tools. | ||