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 cause of this error are incorrect build settings, as indicated by the discussion in the question post comments. This can be fixed by setting “Deployment Postprocessing” back to NO for Debug-Mode (the default value).
In my case the LLDB RPC server consistently crashed every time I ran my app, even after cleaning the build folder and removing and reinstalling Xcode (Version 8.3.3 (8E3004b)) completely. It turned out that apparently LLDB took objection to a breakpoint I had set, just moving this breakpoint by a line resolved the issue.
The target.source-map setting allows you define a series of a => b path remappings in the debug session. It’s not identical to the gdb dir command, which is a list of directories to search for source files by base name, but you can solve the same problems with source-map. Here’s an example where I move … Read more
Did you use Architectures=$(ARCHS_STANDARD_32_BIT) and run your app on a 64 bit device? (iPhone 5S or iPhone 5S simulator) Apple seems to be stricter with apps which don’t support 64bit. So if there is no specific reason, I think it’s better to include arm64 in your build architecture NOTE ABOUT 64-BIT ARCHITECTURE An app extension … Read more
There are two ways to do this in lldb. Most commonly, you use the parray lldb command which takes a COUNT and an EXPRESSION; EXPRESSION is evaluated and should result in a pointer to memory. lldb will then print COUNT items of that type at that address. e.g. parray 10 ptr where ptr is of … 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
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
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