“LLDB crash”

You can put a breakpoint that executes the lldb command and automatically continues somewhere in your app startup code. See https://stackoverflow.com/a/25631359/292145

I have the same problem in XCode 8expression produced error: /var/folders/25/9_sb609576jcmgdbqt553ps08n5b5c/T/lldb/43074/expr40.swift:1:53: error: 'XCUIElement' is not a member type of 'XCTest' $__lldb__DumpForDebugger(Swift.UnsafePointer<XCTest.XCUIElement>(bitPattern: 0x116a0b940).memory) ~~~~~~ ^ /var/folders/25/9_sb609576jcmgdbqt553ps08n5b5c/T/lldb/43074/expr40.swift:1:45: note: while parsing this '<' as a type parameter bracket $__lldb__DumpForDebugger(Swift.UnsafePointer<XCTest.XCUIElement>(bitPattern: 0x116a0b940).memory)

I started getting lldb provided no error string right after I installed Big Sur beta last week.

(lldb) po overlays[0] MKPolyline: 0x60000368bc60 If overlays[0] is in fact a MKPolyline Did you try (overlays[0] as MKPolyline).points()

This worked for me: https://stackoverflow.com/questions/69366799/xcode-13-ios15-is-taking-longer-than-expected-to-launch-it-shows-a-lldb-related

Thank you for the info above, it was very helpful. I think what is happening is that the Xcode 12 LLDB debugger is not working properly on macOS 12. Swift Playgrounds must use the debugger while it executes your code, but since the debugger is not working, it can't execute the playground. There have been a lot of reports of LLDB issues with Xcode 12 on macOS 12. One bug report suggested that you should use Xcode 13 on macOS 12, so please try that and see if that resolves your issue.

Definitely a bug, since your code actually crashes the Swift REPL: Welcome to Apple Swift version 6.0.3 (swiftlang-6.0.3.1.10 clang-1600.0.30.1). Type :help for assistance. 1> import Foundation 2. class Claude { 3. var fieldBeingEdited = 0 4. let kTag = 0 5. 6. @objc func keyboardDone(_ sender : NSObject) { 7. DispatchQueue.main.async { [self] () -> Void in 8. switch fieldBeingEdited { 9. case kTag : break 10. default : break 11. } 12. } 13. } 14. } LLDB diagnostics will be written to /var/folders/z3/53rv5j6x0697yjhjh890hnnr0000gr/T/diagnostics-18fbd0 Please include the directory content when filing a bug report PLEASE submit a bug report to https://developer.apple.com/bug-reporting/ and include the crash backtrace. [ ... stack trace omitted ... ] If I remove the case kTag line, then it has no error.

It seems like we're working through the same book/resource haha. I'm also seeing this error, but I've found that going up the call stack to get out of libsystem_kernel.dylib brings me back to the right context. So: (lldb) expr self (Signals.MainContainerViewController) $R0 = 0x0000000109f083a0 { UIKit.UIViewController = { ... } } (lldb) c Process 8065 resuming (lldb) bt * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP * frame #0: 0x0000000100e04c10 libsystem_kernel.dylib`mach_msg2_trap + 8 frame #1: 0x0000000100e15da4 libsystem_kernel.dylib`mach_msg2_internal + 76 frame #2: 0x0000000100e0ce34 libsystem_kernel.dylib`mach_msg_overwrite + 532 frame #3: 0x0000000100e04f88 libsystem_kernel.dylib`mach_msg + 20 frame #4: 0x00000001803c5ed8 CoreFoundation`__CFRunLoopServiceMachPort + 156 ... (lldb) up 4 frame #4: 0x00000001803c5ed8 CoreFoundation`__CFRunLoopServiceMachPort + 156 CoreFoundation`: -> 0x1803c5ed8 <+156>: mov x26, x0 0x1803c5edc <+

Resolved myself. The debugger indicates date == nil, however, LLDB command po prints out a Date object. Nothing is wrong with DateFormmater.

I have the same problem. Did everything according to the WWDC video and I can trigger execution via lldb _simulateLaunchForTaskWithIdentifier, but other than that, it's never executed. Is there any way to analyze whats going on?

I tried outside of Xcode, attaching the debugger to the Notes app: (lldb) b -[NSView hitTest:] Breakpoint 1: where = AppKit`-[NSView hitTest:], address = 0x0000000183857e18 (lldb) process launch -e /dev/null -- Process 4125 launched: '/System/Applications/Notes.app/Contents/MacOS/Notes' (arm64e) Process 4125 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1 frame #0: 0x000000018c093e18 AppKit` -[NSView hitTest:] AppKit`-[NSView hitTest:]: -> 0x18c093e18 <+0>: pacibsp 0x18c093e1c <+4>: sub sp, sp, #0x70 0x18c093e20 <+8>: stp x24, x23, [sp, #0x30] 0x18c093e24 <+12>: stp x22, x21, [sp, #0x40] 0x18c093e28 <+16>: stp x20, x19, [sp, #0x50] 0x18c093e2c <+20>: stp x29, x30, [sp, #0x60] 0x18c093e30 <+24>: add x29, sp, #0x60 0x18c093e34 <+28>: mov x19, x0 Target 0: (Notes) stopped. (lldb) p $arg1 (unsigned long) $2 = 4312972736 (lldb) po $2 It seems to work in this context.

Solved. Thanks for the reply. In Big Sur, I had previously tried the terminal command tccutil reset AppleEvents and it did not seem to help, although it did remove the approvals of the other apps I had approved in Security & Privacy -> Privacy -> Automation. Later Eclipse IDE would not start at all giving two errors immediately at launch. You do not have permission to open the application 'Eclipse.app' and eclipse quit unexpectedly. Furthermore, Eclipse did not appear in GateKeeper so I could not grant a permission for it to run. I reinstalled Eclipse IDE 2021‑09 from the .dmg provided by the Eclipse organization and found it also fixed my issue running AppleScript from Java, as I was presented with the appropriate requests for permissions when I ran my Java program. Just to answer the reader question... First things first, is your app’s main executable a script? The main executable is a Java class and I run the code from within Eclipse. But that is moot at this point.

*** Assertion failure in -[FBSSerialQueue assertOnQueue], /BuildRoot/Library/Caches/com.apple.xbs/Sources/FrontBoardServices/FrontBoard-619.2/FrontBoardServices/FBSSerialQueue.m:98(lldb)