expr myString = @”Foo” (lldb) help expr Evaluate a C/ObjC/C++ expression in the current program context, using variables currently in scope. This command takes ‘raw’ input (no need to quote stuff). Syntax: expression — Command Options Usage: expression [-f ] [-G ] [-d ] [-u ] — expression [-o] [-d ] [-u ] — expression … Read more
The exception object is passed in as the first argument to objc_exception_throw. LLDB provides $arg1..$argn variables to refer to arguments in the correct calling convention, making it simple to print the exception details: (lldb) po $arg1 (lldb) po [$arg1 name] (lldb) po [$arg1 reason] Make sure to select the objc_exception_throw frame in the call stack … Read more
Simple answer: log messages are not printed, however you can stop at breakpoints, and then print everything using lldb. Run your app While the app is running, go to Debug -> Attach to process by PID or name Write the name of your extension (as bundle-id does not work!?), and click “Attach”. Then run your … Read more
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, … Read more
In case anyone else ever has this question, I finally solved it by adding a breakpoint in NSApplicationMain() (for plain C programs, main() would of course work as well). I set the breakpoint action to process handle SIGUSR2 -n true -p true -s false, and enabled the “Automatically continue after evaluating” option. If anyone has … Read more