“LLDB crash”

This issue is happened with me with MacBook Pro OS Sonoma 14.1.1 and 14.0. When I open the Apple Store and it's selected Discover, close the window, but its not happen for others options. Can you check it Apple?

I'm trying to po an object in lldb and I get the following:(lldb) po fooerror: reference to 'foo' is ambiguouscandidate found by name lookup is 'foo'candidate found by name lookup is 'foo'I have seen references to this error back in Xcode 4.x but nothing recent. Is there a fix for this? I'm using Xcode Version 9.2 (9C40b) and ObjC.

I type in the terminal: lldb$ lldbTraceback (most recent call last): File <string>, line 1, in <module> File /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py, line 98, in <module> import sixImportError: No module named sixTraceback (most recent call last): File <string>, line 1, in <module>NameError: name 'run_one_line' is not definedTraceback (most recent call last): File <string>, line 1, in <module>NameError: name 'run_one_line' is not definedTraceback (most recent call last): File <string>, line 1, in <module>NameError: name 'run_one_line' is not definedTraceback (most recent call last): File <string>, line 1, in <module>NameError: name 'run_one_line' is not definedTraceback (most recent call last): File <string>, line 1, in <module>NameError: name 'run_one_line' is not definedTraceback (most recent call last): File <string>, line 1, in <module>NameE

I'm trying to use a technique we use on Linux to get a stack trace of a process that gets in trouble. We fork a debugger in batch mode in a child process to get the back trace of the parent. When I run this, lldb hangs in the attach to the parent process. And since lldb cannot attach to lldb, there's no way for me to see what's blocking lldb in the attach to the parent. Attached is a simple program that demonstrates the problem. Manually running lldb from a shell with the same arguments gets the stack trace. Is there some way around this hang? #include #include #include #include #include #include static void runChild(pid_t parent) { tconst char *lldb = /usr/bin/lldb; tconst char * args[8]; tchar pidstr[16]; tsnprintf(pidstr, sizeof(pidstr), %d, (int) parent); targs[0] = lldb; targs[1] = --no-lldbinit; targs[2] = --batch; targs[3] = -p; targs[4] = pidstr; targs[5] = --one-line; targs[6] = thread backtrace all; targs[7] = NULL; terrno

Here's a simple C++ program that echoes its arguments... #include int main(int argc, char* argv[]) { for (int i=0; i ./test arg1 #arg2 arg3 0 ./test 1 arg1 2 #arg2 3 arg3 Running under lldb gives this... > lldb ./test arg1 #arg2 arg3 (lldb) target create ./test Current executable set to '/Users/richard/Work/test' (arm64). (lldb) settings set -- target.run-args arg1 #arg2 arg3 (lldb) run Process 6138 launched: '/Users/richard/Work/test' (arm64) 0 /Users/richard/Work/test 1 arg1 Process 6138 exited with status = 0 (0x00000000) I get the same if I quote the arguments, or if I add them to the run line. Stepping into main() we see the argv and args values are as though we only had the first argument. If I quote the second argument and add an initial space #arg1 then it works. I first saw this on an M1 running Sequoia 13.1. It am now on OS 13.3. lldb --version lldb-1600.0.39.109 Apple Swift version 6.0.3 (swiftlang-6.0.3.1.10 clang-1600.0.30.1)