“LLDB crash”

@DTS Engineer I'm not asking for OpenSSL support. I'm asking for help on why lldb hangs when I try to step into an SSL library function. I also want to be clear: we can load the OpenSSL libraries fine. They work fine in macOS < 15. They do not work in macOS 15. lldb hangs in macOS 15. It does not hang in < 15. This all feels like some sort of security measure in macOS 15. I followed your Posting a Crash Report link and it seems to apply to everything except macOS. I don't see any your app crashed dialog, so I don't know if there is information in the system which would help diagnose the problem.

Thanks very much,your answer solved my problem.But when I running again，crash and log is'Message from debugger: The LLDB RPC server has crashed. Please file a bug with Apple with the crash log.'Although the camera is still running,but in console is disconnect and log crash.May be the problem come from version of Xcode 8.0 beta2,besides not reason can explain why the problem appearin the newest version of Xcode

[quote='762334021, hyejunghayat, /thread/762334, /profile/hyejunghayat'] I think It is not crash file coming from my device, but from ios review..? How can I symbolicate crash log that I get from iOS team? [/quote] You can also drag the .crash file onto the Xcode icon and select your app project. Or you can run xcrun crashlog /Path/To/YourApp.crash in Terminal to have LLDB symbolicate it and tell you more information that way. — Ed Ford,  DTS Engineer

Does the crash happen if you start the app within lldb? If not, one way to investigate this is to add a pause call to the start of your app. You can then launch it from the Finder and it’ll stop, at which point you can attach to it from lldb. That should reproduce the problem, because the app was started in the standard environment, while allowing you to investigate it in the debugger. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Here's the output of the debug error when it crashes: I'm also receiving the following failed assertion: wiftData/ModelContext.swift:3253: Fatal error: Failed to identify a store that can hold instances of SwiftData._KKMDBackingData from [:] error: Assertion failed: (byte_size > 0 && byte_size <= 8 && GetMaxU64 invalid byte_size!), function GetMaxU64, file DataExtractor.cpp, line 527 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): 0 LLDB 0x0000000115319aac llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56 1 LLDB 0x0000000114e7a198 lldb_private::lldb_assert(bool, char const*, char const*, char const*, unsigned int) + 148 2 LLDB 0x0000000114e73818 lldb_private::DataExtractor::GetMaxU64(unsigned long long*, unsigned long) const + 72 3 LLDB 0x0000000114d7ded0 lldb_private::CompilerType::GetValueAsScalar(lldb_private::DataExtractor const&

and crash on iOS 7.1 Simulaotor when using Xcode 6.4.In my testing it works with the 7.1 simulator if you target a 64-bit CPU (like iPhone 5s) but fails, as you’ve described, when targeting a 32-bit CPU.I suspect you’re being bitten by a limitation of $arg1, namely, that it always maps to a register. On i386, which is what the 32-bit simulator uses, parameters are passed on the stack, not in a registers, and thus aren’t available via $argXXX notation. Rather, you have to dump the stack and work things out from there. Here’s an example, assuming you’re stopped at the first instruction of objc_exception_throw: (lldb) po $arg1 error: use of undeclared identifier '$arg1' error: 1 errors parsing expression (lldb) # Dump 8 4-bit words in hex from the top of the stack. (lldb) m r -c 8 -s 4 -f x $esp 0xbff3454c: 0x007d5fbb 0x79c55090 0x008de3d0 0x000cc038 0xbff3455c: 0x79c55110 0x00000000 0x008dd82c 0x0091b940 (lldb) # The first word is the return address; the second is th

I searched the Xamarin bugzilla and found this bug that includes a small sample app: https://bugzilla.xamarin.com/show_bug.cgi?id=34631It crashes in the same way our app does within Xcode but runs ok from Finder or when launched from command line lldb.