LLDB crash

The .NET Runtime has shipped an lldb extension that looks to extend LLDB functionality to be able to reason about .NET managed code. This has been working for a long time, but now it fails to load with the error error: this file does not represent a loadable dylib. Loading works if I use a self-compiled version of LLDB. I can't really debug XCode's LLDB, but there are some logs that seemed to hint it was signing checks failing for library validation, but neither Developer nor Application signing would satisfy these. LLDB resides within the XCode bundle at /Applications/Xcode.app/Contents/Developer/usr/bin/lldb. codesign confirms that the bundle enforces library validation. Is there any way to confirm this is the issue? It looks like: Library Validation failed: Rejecting '/*/libsosplugin.dylib' (Team ID: none, platform: no) for process 'lldb(77691)' (Team ID: none, platform: yes), reason: mapped file has no Team ID and is not a platform binary (sig

I've cross posted this at https://stackoverflow.com/q/79647300/6230282 Basically, I use command line and emacs app to develop on daily basis, but all of a sudden, LLDB is invoking Xcode to display source code for me, instead of printing them in command line. How do I switch back? Or alternatively, can I set a custom editor for LLDB? (lldb) version lldb-1700.0.9.502 Apple Swift version 6.1.2 (swiftlang-6.1.2.1.2 clang-1700.0.13.5) About Xcode: Version 16.4 (16F6)

I'm trying to attach with lldb to a x64 process running under Rosetta, attachment itself succeeded but lldb is unable to load target neither it's modules. And getting this output: (lldb) process attach --pid 20586 Process 20586 stopped * thread #1, stop reason = signal SIGSTOP frame #0: 0x00007ff813a1d1ee -> 0x7ff813a1d1ee: jae 0x7ff813a1d1f8 0x7ff813a1d1f0: movq %rax, %rdi 0x7ff813a1d1f3: jmp 0x7ff813a18cdb 0x7ff813a1d1f8: retq Target 0: (No executable module.) stopped. Architecture set to: x86_64-apple-macosx-. (lldb) target modules list error: the target has no associated executable images A few weeks ago I had the same problem, but some combination of actions like rebuilding deleting and redownloading binaries and some other unknown magic fixed this behaviour. And today I stumbled upon this problem again, and same actions does not make any effect. Attaching to process works in general (event to processes running under Rosetta), but this specific process I want to deb

Hi all, Whenever I am trying to build my app on IOS and attach it to a Simulator. The build is getting succeeded but whenever the app is starting to launch on simulator, it is throwing a pop up error - LLDB provided no error string The following error in the popup - Could not launch “XX” Domain: IDEDebugSessionErrorDomain Code: 3 Failure Reason: LLDB provided no error string. User Info: { DVTErrorCreationDateKey = 2024-07-22 04:47:11 +0000; DVTRadarComponentKey = 855031; IDERunOperationFailingWorker = DBGLLDBLauncher; RawUnderlyingErrorMessage = LLDB provided no error string.; } Additionally in the console, this is printed in red in console - Logging Error: Failed to initialize logging system. Log messages may be missing. If this issue persists, try setting IDEPreferLogStreaming=YES in the active scheme actions environment variables. I have tried all things - like restarting Xcode, restarting my Mac, cleaning up my workspace and trying to build again, but nothing helps. I have even

Int this piece of code ****, there are three overloading of the function Func in the class A, but I need to know which of these functions where called in main function.The vtable provide only the memory address of these three functions, but I don't know where I should checkthe foot print of these virtual functions.#include <stdio.h>#include <stdint.h>class A{ public: A(){} virtual ~A() {} virtual int Func(int a) { return puts(__PRETTY_FUNCTION__); } virtual int Func(char a) { return puts(__PRETTY_FUNCTION__); } virtual int Func(float a) { return puts(__PRETTY_FUNCTION__); }};int main(int argc, const char **argv){ A *a = new A(); a->Func(3); return 0;}

Hello, when try to debug assembly code, i am getting the following message: This version of LLDB has no plugin for the language assembler. Inspection of frame variables will be limited. arm64 assembly the code: .data .text .global _area_square _area_square: MUL x0, x0, x0 RET any ideias? thanks.