If control flow is what we're interested in, we can get a really nifty graph view of the procedure. Hopper inserts arrows like these to show control flow, which makes it much easier to follow code. If you scroll down a bit, you'll notice a blue arrow pointing from the je 0x10000197A instruction to its target. Select either the symbol name or the first byte underneath it and mark it as a procedure by pressing the P key (again, no Command key) or clicking Mark As Procedure in the toolbar. The contents of this method start off as "unexplored", so they're displayed as raw bytes.
The one that starts with objc_sel_ is a symbol for the selector, which is less interesting. The one which starts with methImpl_ is the one we want. Press shift-N (no Command key here, Hopper's key commands are a bit eccentric) to get a symbol search window. It's annoying to scroll around searching for it, but of course Hopper knows all about the symbols in your app. Let's find the initWithName:number: method.
#Hopper disassembler 10.15 how to
Fortunately, it's really easy to tell it how to interpret something. In particular, it doesn't identify Objective-C methods as code. It makes some effort to pick out code and treat it as code, but doesn't get everything right. Fundamentally, some sections of the executable are code and some are data, but you can have Hopper interpret any part in any way. Hopper fundamentally treats all bytes in the executable equally. Tell Hopper to open the executable created from the above code, and it will load it and perform some preliminary analysis: These documents can be saved separately, preserving any comments or annotations you've added from one session to the next.Ĭlick Read Executable in the toolbar or select it from the File menu to get started. Hopper has a concept of documents separate from the binaries you inspect. When you first start Hopper, you get a blank document window. clang -framework Cocoa -fobjc-arc test.m #import M圜lass : NSObject
0 kommentar(er)
