LLDB (Swift): Casting Raw Address into Usable Type

IosSwiftLldb

Ios Problem Overview


Is there an LLDB command that can cast a raw address into a usable Swift class?

For example:

(lldb) po 0x7df67c50 as MKPinAnnotationView

I know that this address points to a MKPinAnnotationView, but it is not in a frame that I can select. But, I want to cast the raw address into a MKPinAnnotationView so that I can examine its properties. Is this possible?

Ios Solutions


Solution 1 - Ios

Under Xcode 8.2.1 and Swift 3, the lldb command po or p won't work with the typed variable. You will need to use the swift command print to examine the properties of the typed object instance. (Thanks to cbowns's answer!) E.g.:

expr -l Swift -- import UIKit
expr -l Swift -- let $pin = unsafeBitCast(0x7df67c50, to: MKPinAnnotationView.self)
expr -l Swift -- print($pin.alpha)

Solution 2 - Ios

You can use Swift's unsafeBitCast function to cast an address to an object instance:

(lldb) e let $pin = unsafeBitCast(0x7df67c50, MKPinAnnotationView.self)
(lldb) po $pin

Then you can work with $pin as usual – access properties, call methods, etc.

Check out this article for more information: Swift Memory Dumping.

Solution 3 - Ios

The lldb format for expression seems to have changed in Xcode 7.3. The following got me started:

(lldb) expr -l Swift -- import UIKit
(lldb) expr -l Swift -- let $view = unsafeBitCast(0x7fb75d8349c0, UIView.self)

Solution 4 - Ios

For Custom Classes you need to import your project

expr -l Swift -- import MyTestProject
expr -l Swift --  let $vc = unsafeBitCast(0x7fad22c066d0, ViewController.self)
expr -l Swift -- print($vc.view)

Solution 5 - Ios

Objective-C version

po ((MKPinAnnotationView *)0x7df67c50).alpha

Solution 6 - Ios

As of Xcode 8/Swift 3, here's what worked for me. (This is based off @sfaxon's answer.)

(lldb) expr -l Swift -- import UIKit
(lldb) expr -l Swift -- let $nav = unsafeBitCast(0x1030ff000, to: UINavigationController.self)

Solution 7 - Ios

Thanks to all the answers above, unsafeBitCast also works well with Xcode 8.3.2 / Swift 3 / macOS / Cocoa Application.

Memorize an address of current instance

(lldb) p tabView.controlTint
(NSControlTint) $R10 = defaultControlTint

(lldb) p self
(LearningStoryboard.NSTabViewController) $R11 = 0x00006080000e2280 {
.....

Later, examine them

(lldb) p unsafeBitCast(0x00006080000e2280, to: NSTabViewController.self).tabView.controlTint
(NSControlTint) $R20 = graphiteControlTint

(lldb) p $R11.tabView.controlTint
(NSControlTint) $R21 = graphiteControlTint

If something like this happens

(lldb) p unsafeBitCast(0x00006080000e2280, to: NSTabViewController.self).tabView.controlTint
error: use of undeclared identifier 'to'

(lldb) p $R11.tabView.controlTint 
error: use of undeclared identifier '$R11'

make sure that choose one of the stack frames of Swift source code rather than assembler one.

It is likely to happen when the application was paused by clicking a Pause button or stopped with an exception. By choosing a stack frame accordingly, let lldb infer a proper programing language.

Solution 8 - Ios

@Xi Chen's answer works perfectly when your LLDB session was started in a Swift context. However, in some cases you might have stopped in a breakpoint outside a Swift context; for example, when it's a symbolic breakpoint to Objective-C API, or when in Debug View Hierarchy mode (at least as of Xcode 11.4).

error: unknown type name 'let'
error: use of undeclared identifier 'unsafeBitCast'

In that case, you'll need to do it the old way using Objective-C:

e MKPinAnnotationView *$pin = (MKPinAnnotationView *)0x7df67c50

and now you can use $pin as you would.

Solution 9 - Ios

It took me longer to figure out that I'd like to admit. It's similar to @afinlayson answer, but with better explanation (I hope!) and fixed syntax

If you want to check properties of an objects using Xcode’s view hierarchy debugger then this will work: You’re in objc context by default so you’ll have to switch it to Swift context

  1. First import your project (if you want to use some of the classes defined there)

expr -l Swift -- import <YOUR PROJECT NAME>

  1. Cast object using it’s memory address to whatever class you want

expr -l Swift -- let $vc = unsafeBitCast(0x7fb7c51cb270, to: <YOUR PROJECT NAME>.<YOUR CUSTOM CLASS NAME>.self)

  1. Access any value you want from the object

expr -l Swift -- print($vc.<PROPERTY NAME>)

Example:

expr -l Swift -- import Football

expr -l Swift -- let $vc = unsafeBitCast(0x7fb7c51cb270, to: Football.Ball.self)

expr -l Swift -- print($vc.velocity)

Solution 10 - Ios

The easiest way, swift 4

expr unsafeBitCast(0x7df67c50, to: MKPinAnnotationView.self)

Solution 11 - Ios

po is an alias, which means it can be overridden. You can override po by handling hex addresses using objc:

command regex po
s/(0x[[:xdigit:]]+)/expression -l objc -O -- %1/
s/(.+)/expression -O -- %1/

To see what effect this has, you can tell lldb to expand these aliases:

(lldb) settings set interpreter.expand-regex-aliases true

Also I have created https://github.com/kastiglione/swift_po, which is a substitute po for Swift. It handles object addresses, and has a few other improvements too.

Solution 12 - Ios

When in Swift lldb context and dealing with NSObject subclass such as MKPinAnnotationView it's arguably easier to deliberately switch back to obj-c lldb context using this 1-liner:

e -O -l objc -- 0x7df67c50

where e -O -- is equivalent to po in lldb when in obj-c context.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionjarrodparkesView Question on Stackoverflow
Solution 1 - IosXi ChenView Answer on Stackoverflow
Solution 2 - IosgregheoView Answer on Stackoverflow
Solution 3 - IossfaxonView Answer on Stackoverflow
Solution 4 - IosafinlaysonView Answer on Stackoverflow
Solution 5 - IosrockhardView Answer on Stackoverflow
Solution 6 - IoscbownsView Answer on Stackoverflow
Solution 7 - IosToraView Answer on Stackoverflow
Solution 8 - IosGobeView Answer on Stackoverflow
Solution 9 - IosBartosz KunatView Answer on Stackoverflow
Solution 10 - IosKingsley MitchellView Answer on Stackoverflow
Solution 11 - IosDave LeeView Answer on Stackoverflow
Solution 12 - IosKamil.SView Answer on Stackoverflow