lldb
Setting disassembly flavour to Intel in LLDB
The exact line to write in your ~/.lldbinit file is settings set target.x86-disassembly-flavor intel In the future, you will also be able to tweak how immediate values are displayed with the new settings: target.use-hex-immediates and target.hex-immediates-style.
Cannot debug Swift module/framework embedded in Objective-C app
For me it was just as simple as it was painful and time consuming: import SDWebImage was the PROBLEM, because one of the frameworks had the SDWebImage already packed in it(and I couldn’t see it), and that framework happened to be Objective-C, and the app was Swift. I also added the SDWebImage to the project, … Read more
How can I do remote debugging in Xcode 4?
Xcode 4 doesn’t currently support remote Mac debugging. Even if you were able to hack Xcode to talk to a remote debugserver, there’s no guarantee that interaction with it would be fully or properly handled by the IDE or the remote debugserver.
error: Couldn’t IRGen expression, no additional error [duplicate]
I had same issue with Carthage. However while looking more closely at console I’ve spotted that Carthage instead of building RxSwift just downloaded pre-built binaries, *** Downloading RxSwift.framework binary at “Zürich” that in turn contribute to IRGen error. So forcing Carthage to build framework instead of downloading binary worked. carthage update –platform iOS –no-use-binaries
What is the lldb equivalent of gdb’s –args?
Yes, it’s just — instead of –args. From the help: lldb -v [[–] <PROGRAM-ARG-1> [<PROGRAM_ARG-2> …]] Thus: $ lldb — exe –lots –of –flags -a -b -c d e
Open .NET Core 2.0 dump in lldb on Linux – which lldb version?
Quite old question, but maybe this helps someone: E.g. Dockerfile to include lldb and into asp dotnet 3.1 FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 WORKDIR /vsdbg RUN apt-get update \ && apt-get install -y –no-install-recommends \ unzip \ procps \ lldb-3.9 \ && rm -rf /var/lib/apt/lists/* \ && curl -sSL https://aka.ms/getvsdbgsh | bash /dev/stdin -v vs2019 -l /vsdbg WORKDIR … Read more
lldb: Couldn’t materialize: couldn’t get the value of variable
That error means the debug information does mention the variable, but says it has no storage location at the current PC. That can be because the variable got optimized out (unlikely given you are just calling a function on the variable) or because the compiler flubbed the debug info for the variable and lost track … Read more