“LLDB crash”

I'm using Xcode 12 beta 3. When running my Apple Watch's target on WatchOS 7, I get this error: Warning: Error creating LLDB target at path '/Users/evan/Library/Developer/Xcode/DerivedData/audigo-cneguthkmmoulfgcprsazbryrlrl/Build/Products/Debug-watchsimulator/AudigoWatchApplication.app'- using an empty LLDB target which can cause slow memory reads from remote devices. I know this error use to be when running 32 bit frameworks on 64 bit devices, but I'm not doing that. Is this a bug? Or is there a setting I don't know of that needs to be updated?

Hi,I'm just starting to learn Swift and in the Playground area, I have come to a little problem.This is my code:/ import UIKit var str = Hello, playground class Person { init (){ println(A new person has been created) } func sayCheese(){ println(Cheese!) } } var b = Person() b.sayCheese()At line 17. adn 16. it says __lldb_expr_54.Person - I'm not really sure what this means but to my prior coding knowledge, there shoudl't be anything wrong? Unless C is very different to Java.Would really help if you could explain what is wrong and why its wrong!Thanks

Hello ,I'm faced to this problem -[UIImage class]: message sent to deallocated instance 0x7fe0f349ac10(lldb)

In our project (~ 40.000 LOC) we experience a very slow initial expression evaluation when using commands like po myVariable in LLDB or breakpoint actions using @expr@: It often takes more than 20 seconds for initial evaluation, further evaulations then take only a fraction of a second.We think this is due to the unwinding of the app context and doing a expression -L swift -O -- myVariable in the background, as commands like frame variable myVariable are much faster also on first call (~ 100 ms).However, because of that using breakpoint actions is no fun, and as the codebase is not that big: Is there any way to determine the cause of these slow initial evaluations, e.g.- caused by embedded (Objective-)C(++) libraries- Access of specific frameworks like AVFoundation- ...Any help is appreciated.

` func submitBackgroundTasks() { // Declared at the Permitted background task scheduler identifiers in info.plist let backgroundAppRefreshTaskSchedulerIdentifier = com.FeedX.backgroundAlerts let timeDelay = 10.0 do { let backgroundAppRefreshTaskRequest = BGAppRefreshTaskRequest(identifier: backgroundAppRefreshTaskSchedulerIdentifier) backgroundAppRefreshTaskRequest.earliestBeginDate = Date(timeIntervalSinceNow: timeDelay) try BGTaskScheduler.shared.submit(backgroundAppRefreshTaskRequest) print(Submitted task request) } catch { print(Failed to submit BGTask) } } I am able to submit the task and hit the breakpoint but in the LLDB i try to simulate the task using the command e -l objc -- (void)[[BGTaskScheduler sharedScheduler] _simulateExpirationForTaskWithIdentifier:@com.FeedX.backgroundAlerts] But i get the following error : error: Error [IRForTarget]: Rewriting an Objective-C constant string requires CFStringCreateWithBytes Any idea on how to solve this or run the task using a different way? Thanks.

Xcode 12.4 on Big Sur, a very basic attempt to launch and debug a process. Little-Net:host-osx minfrin$ lldb ./tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing (lldb) target create ./tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing Current executable set to '/Users/minfrin/src/redwax/open-eid/chrome-token-signing-trunk/host-osx/tmp_firefox/Library/Google/Chrome/NativeMessagingHosts/chrome-token-signing.app/Contents/MacOS/chrome-token-signing' (x86_64). (lldb) process launch -i cert.native error: process exited with status -1 (attach failed (Not allowed to attach to process. Look in the console messages (Console.app), near the debugserver entries when the attached failed. The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.)) Why would lldb, running as my local user, be unable

Trying to run a React Native app via Xcode can be very very very slow. Excruciatingly so. I often see messages saying things like Launching app is taking longer than expected. LLDB is likely reading from device memory to resolve symbols. But I see this all the time, if that's what it's doing it never finishes, and does it every time. This isn't just with one phone, its with several. Is it possible there some fundamental conflict between Xcode and LLDB and React Native Metro trying to communicate / load / debug / whatever that slows things down to a standstill?