I was having the same issue using Carthage frameworks, and got the LLDB debugger working again by deleting the Carthage folder in the project root and forcing Carthage to rebuild the frameworks from source: carthage update –platform iOS –no-use-binaries
You can access it by p (CGRect)[view bounds] or p view.layer.bounds view.bounds is actually view.layer.bounds It seems that the type info of [UIView bounds] is not available to lldb
Silly me, I was in the ‘Target Output’ window instead of the ‘Debugger Output’ window. Somehow I thought I checked the other console windows there, but apparently I didn’t.
Use breakpoint set -E c++ to break on all exceptions and breakpoint set -F std::range_error to break on a specific exception.
To complement Michael’s answer. I tend to use: memory read -s1 -fu -c10000 0xb0987654 –force That will print in the debugger. -s for bytes grouping so use 1 for uint8 for example and 4 for int -f for format. I inherently forget the right symbol. Just put the statement with -f and it will snap … Read more
LLDB is part of the LLVM suite of tools that Apple is moving to, including Clang. There are tons of improved features, including improved performance. There’s a quick intro for GDB users here: http://lldb.llvm.org/tutorial.html However… You might want to take a trip over to the forums at developer.apple.com. There’s a fair bit of rumbling about … 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
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 canonical reference for gdb v. lldb commands is http://lldb.llvm.org/lldb-gdb.html You want to use the expr command which evaluates an expression. It’s one of the lldb commands that takes “raw input” in addition to arguments so you often need a “–” to indicate where the arguments (to expr) end and the command(s) begin. e.g. (lldb) … 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