LLDB crash

[quote='852111022, MrZnuk, /thread/794920?answerId=852111022#852111022, /profile/MrZnuk'] If you have any tips or guidelines, I'll gladly take them :) [/quote] And I’m happy to offer them (-: Mac users expect apps to act like apps. If you double click an app, it should present a UI. But they also understand app lifetimes. If the user starts a long-running task in the app, they expect the task to be tied to the lifetime of the app. So, if they quit the app, it wouldn’t come as a surprise for if that cancels the task. Most apps like this will present a ‘Are you sure you want to quit?’ alert in this case, just to be sure. If you want to separate the code into two separate processes, that’s fine. I see two common reasons for this: Security — You want to restrict or extend what resources this code has access to. Reliability — You don’t want a crash in this code to take out your entire app. There are two common ways to do this: Put the code in an XPC service. Or a helper process. Or a helper app. App-scope

Checking for crash logs was the hint I needed. I think I found the problem. Thanks!

We're unable to work with this crash report as we need to see the complete symbolicated Apple crash report with its original formatting preserved. Please post the complete symbolicated Apple crash report as an attachment to preserve its formatting. Posting a Crash Report explains how to do so. You also wrote: In our application, we have seen a sharp rise in crashes in BaseBoard and FrontBoardServices, which are internal iOS frameworks, since we migrated our app to use UIWindowSceneDelegate. If you haven't already, it might be worth looking into how you've setup your SceneDelegate. TN3187: Migrating to the UIKit scene-based life cycle is a good starting point to compare against to see what you're doing differently.

Indeed... The original issue, which was fixed in iOS 18.4, doesn't sort with an optional relationship. I see this crash a different issue. Do you have a feedback report yet? If not, would you mind to file one for us and share your report ID here? Thanks! Best, —— Ziqiao Chen  Worldwide Developer Relations.

Ah, sorry, I missed a key point of state in your previous response. Hiding all the important stuff in a text attachment is… well… innovative )-: [quote='851786022, Peter_Si, /thread/789165?answerId=851786022#851786022, /profile/Peter_Si'] The VPN session failed because an internal error occurred. [/quote] Hmmm, that’s weird, and also not good. Writing datagrams to the flow shouldn’t be hard. A message like this: IPCConnection Starting XPC listener for mach service suggests that something crashed and had to be restarted. Such a failure would also be a good candidate for the internal error quoted above. Do you see any crash reports generated? Either for your sysex or for various NE helper processes? If you see one, please post it here. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I think we have also encountered this same problem when loading a webpage: https://www.verovio.org/index.xhtml Thread 0 Crashed: 0 WebCore 0x1b70590ec WebCore::PendingCallbacks::appendCharactersCallback(std::__1::span) + 76 1 WebCore 0x1b406f54c WebCore::charactersHandler(void*, unsigned char const*, int) + 180 2 libxml2.2.dylib 0x19869b238 xmlParseCharData + 2168 3 libxml2.2.dylib 0x198693eac xmlParseTryOrFinish + 4380 4 libxml2.2.dylib 0x1986924a0 xmlParseChunk + 712 5 WebCore 0x1b406e180 WebCore::XMLDocumentParser::doWrite(***::String const&) + 228 6 WebCore 0x1b7056614 WebCore::XMLDocumentParser::append(***::RefPtr, ***::DefaultRefDerefTraits>&&) + 108 7 WebCore 0x1b5bb03e8 WebCore::DecodedDataDocumentParser::appendBytes(WebCore::DocumentWriter&, std::__1::span) + 208 8 WebCore 0x1b628378c WebCore::DocumentLoader::commitData(WebCore::SharedBuffer const&) + 1668 9 WebKit 0x1b8af54e8 WebKit::WebLocalFrameLoaderClient::committedLoad(WebCore::DocumentLoader*, WebCore::SharedBuf

Our engineering teams need to investigate this issue, as this might indicate an issue with iOS 26. We'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating a successful bug report.

Our engineering teams need to investigate this issue, as this might indicate an issue with iOS 26. We'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating a successful bug report.

When you build your app for release, what does the on-disk structure look like. For example, here’s what I see when I build a project I created rom one of Xcode’s built-in templates: % find Test795348 04-08-2025, 10.47.xcarchive/Products/Applications/Test795348.app …/Test795348.app …/Test795348.app/_CodeSignature …/Test795348.app/_CodeSignature/CodeResources …/Test795348.app/Test795348 …/Test795348.app/embedded.mobileprovision …/Test795348.app/Info.plist …/Test795348.app/PkgInfo Specifically, I’m interested in the final disposition of your Mach-O images. Feel free to elide anything that’s not directly related to that, such as your resources. Also feel free to redact any private info you don’t want to share. In Posting a Crash Report I describe a simple redaction scheme that I’ve found works well for artefacts. The reason I’m asking this is that iOS imposes some strict limits on how you can embed code within an iOS app. See Placing Content in a Bundle for info about that. And, quoting that doc: If you

Right. In general the compiler should not crash. No matter what you throw at it, it should either work or emit a helpful error. So, this sort of crash is, by definition, bugworthy. Bug Reporting: How and Why? has lots of hints and tips about how to file effective bug reports. In this case, I have some specific recommendations: Test with the current Xcode 26 beta. Swift moves forward quickly, so it’s possible that this bug is already fixed there. If it still crashes, try to isolate the problem into a small test project and attach that to your bug report. That’ll greatly assist with the investigation. If you can’t isolate it, you might consider adding your entire project to the bug report, or uploading it to a public repository and adding that URL. I understand, however, that this isn’t always possible. Make sure you include a full build log with your bug report. For advice on how to get that, see Command [something] failed with a nonzero exit code. And, as to reiterate darkpaw’s note

I have played around a bit more with the code: I tried passing pointers to the functions themselves Making sure the callbacks are called from the mainthread But nothing seems to work. I did stumble into this page though https://developer.apple.com/documentation/xcode/investigating-memory-access-crashes#Use-VM-Region-Info-to-locate-the-memory-in-your-apps-address-space And it's useful to understand the crash logs. My full crash is: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 Exception Codes: 0x0000000000000002, 0x0000000000000000 VM Region Info: 0 is not in any region. Bytes before following region: 4307271680 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 100bbc000-100bc0000 [ 16K] r-x/r-x SM=COW /var/containers/Bundle/Application/D7CA13B9-71D1-467E-882D-317F9AF57049/OpacityPod_Example.app/OpacityPod_Example Termination Reason: CODESIGNING 2 Invalid Page So it's clearly