LLDB crash

Same issue for me since the latest updates to Sequoia 15.4 and 16.2. Whenever I attach to a Simulator and try to view any variable, the LLDB RPC server crashes immediately. FB16682372 Debugging physical devices still seems to work fine.

Looks like a bug, not new....See https://stackoverflow.com/questions/43635522/what-is-lldb-rpc-server-when-does-it-crash-in-xcode-why-it-crashesIf you take the time to file one, be sure to add your report # to your thread for reference, thanks and good luck.Ken

Signal 6 is SIGABRT, which likely means that something called abort() in your app. When this happens and you get that message in Xcode, you can review the thread backtraces in the debugger to see what aborted. Alternatively, you can enter the LLDB command detach, which will detach the debugger, and allow the app to continue to crash using normal means, resulting in a crash report that you can then review. — Ed Ford,  DTS Engineer

I have do this.If I take the name from my storyboard and run the app, crash and sgabrt.If I take the name Main, I becoes this error:2015-08-22 09:47:35.911 Kapitel2[1168:47555] [+] <ViewController: 0x7ba78de0>.writeLog:(lldb)So whats now?

@DTS Engineer On disabling the signal handler I was able to get a crash report. ... which suggests you have a Mach exception handler that’s active even with your signal handler disabled. Is it possible to disable that? No, the exception handler is crucial to the operation of the product. Remember this is a language. We produce compiled code, catch exceptions on behalf of users, etc. This has been part of the product since the first version, in MacOS 10.0. For example, in Common Lisp, we have an API for virtual multi-threading and that facility uses the exception handler for its operation. That feature cannot be turned off. Our application is not a normal application. We have an entire programming system inside our product, and that includes catching exceptions and dealing with them programmatically. Implementing a Mach exception handler correctly is really hard, We agree. We would be happy to send you the source code for it, but we don't want to post it here. This exception handler is as old as MacOS

OS X v10.11 Developer beta Release notes Known IssuesXcode 6.x has known compatibility issues when run on OS X El Capitan. It is strongly encouraged that you use Xcode 7 when running on OS X El Capitan.Xcode processes may quit unexpectedly if older iOS Simulator runtimes (Xcode 6.x) are present on disk.seems pretty clear to me

Same here: lldb started crashing with simulator on encountering breakpoints, as of right now it even seems to crash reliably after some time. It seems to work properly on physical device Sequoia 15.4, XCode 16.2, iPhone 16 pro simulator 18.2 If that matters: I use github copilot xcode extension and that one also has issues => chat assistant crashes a lot and forces me to relaunch xcode every couple requests report.txt

Not sure it's your problem, but the latest beta release notes say this... SwiftUI ...Known Issues ......ProgressView generic type signature has changed, adding the ProgressViewStyleConfiguration.CurrentValueLabel generic parameter. This change does not require any source changes, but will cause apps you compile using an earlier beta SDK to quit unexpectedly. (63580200) You might want to file bugs and wait for next beta/release.