LLDB crash

Has anyone has this error when trying to run a watchOS 2 app on a connected phone and watch:Warning: Error creating LLDB target at path '/Users/user/Library/Developer/Xcode/DerivedData/app-cuurdvsnbtcffcgnbrqkwlimkdjj/Build/Products/Debug-iphoneos/App WatchKit Extension.appex'- using an empty LLDB target which can cause slow memory reads from remote devices.Would love to know if there's a fix to this.

We are updating our macOS projects for Universal binaries and our two main apps fail to debug in Xcode 12.2 (on Big Sur), but I can use lldb from the command line to run the built app. When I try to run the app in the debugger in Xcode I get this error: Warning: Error creating LLDB target at path 'my app path'- using an empty LLDB target which can cause slow memory reads from remote devices. error: failed to launch '2687' -- LLDB provided no error string I assume the number is the PID, it changes each time I try to run the debugger. Not sure what to do.

hello, i can't fix this error displayed in the return line(lldb)int main(int argc, char *argv[]) { return UIApplicationMain(argc, argv, nil, NSStringFromClass([PoutremultivueAppDelegate class])); }

If I build an x64 binary on my M4 Mini, when I try to debug it using Visual Studio remote debugging the connection is closed, which means I cannot debug my code in x64 mode. I need to be able to do this as I have architecture specific code. I have Rosetta installed. FWIW I have the same issue with lldb-mi :( David

Env: Monterey 12.6.5, Xcode 14.0.1 Recent update for xcode. Straight forward declaration of bitset, but a large one. std::bitset<1048567> bs ; Running code in xcode, suddenly started getting lldb notice Message from debugger: The LLDB RPC server has exited unexpectedly. You may need to manually terminate your process. Please file a bug if you have reproducible steps. upon entering the function itself, not when executing the bitset declaration line. Moved the declaration to main, and still lldb notice. Then noticed bitset size in debugger dialog is 256 (see snippet image), although the bitset's real size is as declared (debugger shows real size in parentheses, but only show first 256 bits). Checked vector, it is show and represents in full. Duplicated on Ventura 13.3.1, Xcode 14.2. Suspect the LLDB issue was from changing bitset size to pow(2,64) before, which compiles, but generates thread EXC_BADACCESS ... error/warning. Two issues: first, why only display first 256

Hi Experts,I can add WaitForDebugger to file in /Library/LaunchDaemon/*.plist to debug launch daemons from scratch with LLDB.Is it possible to debug a system extension from scratch with LLDB? Thanks a lot.

I am building simple command-line programs in C. When I run LLDB on the command line on any such executable , even though I set a breakpoint in main, LLDB always runs to termination and reports an error. Below is an example: ~ % clang -Wall -g prog.c -o prog aviram@csaamdS278stma ~ % lldb prog (lldb) target create prog Current executable set to '/Users/aviram/prog' (x86_64). (lldb) breakpoint set --name main Breakpoint 1: where = progmain + 15 at prog.c:73:21, address = 0x0000000100003ebf (lldb) run Process 99926 launched: '/Users/aviram/prog' (x86_64) Process 99926 exited with status = -1 (0xffffffff) lost connection (lldb) ` Note that it says lost connection even though I am _ remote debugging. This happens with every executable I build._ Details: 2019 MacBook Pro (x86_64, Sonoma); Apple Clang 12.0.0 (downloaded with Xcode 15.0.1). Why is this happening and what can I do to debug my program (for real) using LLDB from the command line? T

In some particular situation, Xcode debugger or lldb cli cannot correctly extract some value that returned by a async throw function and handled by guard let try?. Here is the minimum example: import Dispatch func test() async throws -> [Int] { return [369] } let group = DispatchGroup() group.enter() let task = Task { guard let res = try? await test() else { return } print(res) group.leave() } group.wait() If added a break point at print(res), the debugger cannot show the value of res. Due to forum limitation, I cannot paste a screenshot here... if use p res or po res at lldb cli, it shows: (lldb) p res error: expression failed to parse: error: :3:1: error: cannot find 'res' in scope res ^~~ (lldb) po res error: expression failed to parse: error: :3:1: error: cannot find 'res' in scope res ^~~ If test() returns a dict, or a costom struct, the issue retains. But if returned a trivial value like Int, it acts normally. Also, if remove the guard statement, make res a optiona

As I was watching WWDC19 Session: LLDB: beyond po I got confused about p command. In the session there was a following example to show how p command works: // Struct for demonstration purposes struct Trip { var name: String var destinations: [String] let cruise = Trip ( name: Mediterranean Cruise destinations: [Sorrento, Capri, Taormina]) Using p to get info about cruise instance: (lldb) p cruise (Travel.Trip) $R0 = { name = Mediterranean Cruise destinations = 3 values { [0] = Sorrento [1] = Capri [2] = Taormina } } I was following along and wrote the same code. But the output from LLDB turned out to be different: (lldb) p cruise (LLDB_Apple_Session_FollowAlong.Trip) { name = Mediterranean Cruise destinations = 3 values { [0] = Sorrento [1] = Capri [2] = Taormina } } As you can see LLDB didn't create a global variable R0 which I could later use in my debugging session and that seemed strange to me. Then the presenter said the following: p is just an alias for the