LLDB crash

Chrome has started crashing almost immediately after startup. I've reported the issue to the Chrome team here: https://issues.chromium.org/issues/385433270 I'm hoping to debug the issue a bit more myself. This page from the Chrome team https://chromium.googlesource.com/chromium/src/+/master/docs/mac/debugging.md#chrome-builds suggests using the follow to strip off the protections: codesign --force --sign - path/to/Google Chrome.app However, applying that seems to have no effect: % codesign --force --sign - /Applications/Google Chrome copy.app /Applications/Google Chrome copy.app: replacing existing signature /Applications/Google Chrome copy.app: resource fork, Finder information, or similar detritus not allowed % lldb /Applications/Google Chrome copy.app (lldb) target create /Applications/Google Chrome copy.app Current executable set to '/Applications/Google Chrome copy.app' (arm64). (lldb) run error: process exited with status -1 (attach failed (Not allowed to attach to pr

Hi, I am working on a quite huge source code in which the breakpoint function is critical but unfortunately, XCode does not hit the breakpoint. To illustrate the problem clearly, I simplified the step to help you reproduce. XCode version: 12.5 OSX version: 11.3 Steps: 1, Pull the source of WebRTC, build it with is_debug=true and symbol_level=2 I ran the steps below: Note: This forum does not allow me to post the actual link, so please let me post how to reach there. A Viste webrtc.org/support/overview B Select Native development in the left pane. C Select iOS link on the page. D Go through the steps till and include Using Xcode 2, I open the XCode project and select AppRTCMobile , set the breakpoint at main.m, and hit the play button, XCode did build the source yet the breakpoint does not get hit. 3, I suspected that the problem might be the ninja build code inside the huge source, so I made an experiment using lldb to load the binary, it is actually working, here is the copy of messages: Load the ap

Xcode version: 12.3 (12C33) Apple M1 Device, On running an app through Xcode lldb server is crashing. Process: lldb-rpc-server [35042] Path: /Applications/Xcode.app/Contents/SharedFrameworks/LLDBRPC.framework/Versions/A/Resources/lldb-rpc-server Identifier: lldb-rpc-server Version: 1205.0.11.1 Code Type: ARM-64 (Native) Parent Process: Xcode [91389] Responsible: Xcode [91389] User ID: 501 Date/Time: 2021-02-11 09:13:32.670 +0530 OS Version: macOS 11.0 (20A2411) Report Version: 12 Anonymous UUID: 0EECC9B3-B670-EE4C-4C01-5167159E1F56 Sleep/Wake UUID: D137B035-CA2E-4AD8-9CC0-8CB1247AC472 Time Awake Since Boot: 100000 seconds Time Since Wake: 140 seconds System Integrity Protection: enabled Crashed Thread: 6 lldb.process.internal-state(pid=38840) Exception Type: EXC_BAD_ACCESS (Code Signature Invalid) Exception Codes: 0x0000000000000032, 0x000000016b6e8000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace CODESIGNING, Code 0x2

I'm getting the error: ** Warning: Error creating LLDB target at path '/Users/tantan/Library/Developer/Xcode/DerivedData/Videe-bpukzfmjaxewiuaiolulcqllukjg/Build/Products/Debug-iphonesimulator/[AppName].app'- using an empty LLDB target which can cause slow memory reads from remote devices.** Is there anyone who can explain to me what the reason is and how can fix it? Thanks,

Hi, I am using Mohave 10.14.6 on a work computer with XCode 11.2 having recently been upgraded from High Sierra. Before the upgrade, I had been successfully using lldb-mi as part of my cross-platform C++ debugging sessions; this binary file had been present in the /Applications/Xcode.app/Contents/Developer/usr/bin folder before the upgrade. After the upgrade, lldb-mi is gone! How do I get it back? I see this is also happening to Catalina developers (not just Mohave). There are bugs debugging certain C++ elements in lldb thus the need for lldb-mi. How do I get lldb-mi back? A quick look through /usr/local/bin and other spots didn't locate it either unless I missed something? Thanks in advance for anyone's help.

Here's a simple C++ program: cpp #include stdio.h int main() { printf(Hello worldn); return 0; } On my M1 Macbook air, I can compile, run, and debug this program successfully: bash % clang++ hello.cpp -g % ./a.out Hello world % lldb a.out (lldb) target create a.out Current executable set to '/Users/sam/build/a.out' (x86_64). (lldb) run Process 55681 launched: '/Users/sam/build/a.out' (x86_64) Hello world Process 55681 exited with status = 0 (0x00000000) When adding -arch arm64, it builds and runs, as expected: bash % clang++ hello.cpp -g -arch arm64 % ./a.out Hello world But debugging seems to fail: bash % lldb a.out (lldb) target create a.out Current executable set to '/Users/sam/build/a.out' (arm64). (lldb) run error: process exited with status -1 (attach failed ((os/kern) invalid argument)) Is there anything special I need to do to get lldb to work with an executable compiled with -arch arm64? Macbook Air (M1, 2020) Big Sur 11.0.1 bash % clang+

Ever since updating to Xcode 16.3, auto-completing variable names in lldb does not work. Is this a known bug? Is there a workaround to get it do auto-complete again?