“LLDB crash”

Edit: (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 (lldb) c Process 4125 resuming -- later Process 4125 stopped * thread #1, queue = 'com.apple.main-thread', stop

Tested on iOS 14 and 15: (lldb) po message ok

I am also getting$ swiftdyld: Library not loaded: @rpath/LLDB.framework/LLDB Referenced from: /Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2016-03-24-a.xctoolchain/usr/bin/lldb Reason: image not foundTrace/BPT trap: 5Any help will be highly appreciated !

Apparently I had set the data incorrectly. It builds now, reading:guard let userId = authResult?.user else { return } let userData: [String: Any] = [ firstName : , User ID : userId, dateCreated : FieldValue.serverTimestamp(), ] let db = Firestore.firestore() db.collection(users).document(one).setData(userData) { err in if let err = err { print(Error writing document: (err)) } else { print(Document successfully written!) } } } } }But, it crashes and gives a runtime error:@UIApplicationMain class AppDelegate: UIResponder, UIApplicationDelegate { //error: //libc++abi.dylib: terminating with uncaught exception of type NSException //(lldb) //3 comments above all one lineDo you know what this crash means?

For an OS X app you can use the lldb.macosx.crashlog package, as described in Symbolicating with LLDB. I don’t know if this works in the iOS Simulator but it’s worth a try. Even if it doesn’t work, the package is written in LLDB’s scripting language, Python, so you can crib it for ideas as to how to move forward. If Xcode is installed in the default place, the path is /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/Python/lldb/macosx/. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Is it worth filing a bug report without a sample project? I talked with the LLDB team about this and the answer was an emphatic “Yes!” So please file the bug with whatever info you have available. One thing you can do to help out here is enable LLDB’s logging and attach a log file to your bug report. First add this to your .lldbinit file: % cat ~/.lldbinit log enable -f /tmp/lldb.log lldb types expr I’m using /tmp/lldb.log but use whatever path works for you. If you’re using Xcode, make sure that lldb-rpc-server picks up this change. The easiest way to do that is to quit and relaunch Xcode. Finally, reproduce the problem and, once your done, gather up the log and attach it to your bug. Thanks in advance! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Also lldb-rpc-server eats a lot of RAM - 8GB and more...

I had a very similar issue only when I try to print test related objects at the debugger prompt(but it works normally If I just run the test and don't breakpoint with the debugger)(I'm using Xcode 8.2.1)for example:I set a breakpoint just after this line: let app = XCUIApplication()and then try(lldb) po appexpression produced error: error: /var/folders/y0/1ghrk5gn4911s6kwq6n1ny8w0000gn/T/./lldb/2506/expr33.swift:1:72: error: 'XCUIApplication' is not a member type of 'XCTest'Swift._DebuggerSupport.stringForPrintObject(Swift.UnsafePointer<XCTest.XCUIApplication>(bitPattern: 0x1214213b0)!.pointee) ~~~~~~ ^but when I check debugDescription, it works(lldb) po app.debugDescriptionAttributes: Application 0x608000176500: {{0.0, 0.0},..then surprisingly, the same command that failed above works now successfully!(lldb) po appAttributes: Application 0x608000176500: {{0.0, 0.0}, {375.0, 667.0}}..I don't understand why, but it seems a workaround.

One thing that may be happening here is that your app is launching without the debugger attached, which is where Quinn's points about the system log come in. You can use the macOS Console app to look for your logs once you're using OSLog. Something I like to do in addition to that is configure LLDB to wait to attach until your process is launched. That way, when you use Siri to launch the app, the logs you're expecting will be picked up in the LLDB console. You can configure this in your Xcode scheme, under the Run options. With that configuration set, if you press the Run button in Xcode, the system starts LLDB, but not your app like usual when you press the Run button. You can then launch your app through Shortcuts or Siri, LLDB will now attach automatically, and record all of your OSLog statements inside of Xcode for that launch sequence. — Ed Ford,  DTS Engineer

It seems rather determined to run python3:# /usr/bin/lldb -P/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python3# /usr/bin/lldb --versionlldb-1100.0.30.12Apple Swift version 5.1.3 (swiftlang-1100.0.282.1 clang-1100.0.33.15)However:# /Library/Developer/CommandLineTools/usr/bin/lldb -P/Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/Python# /Library/Developer/CommandLineTools/usr/bin/lldb --versionlldb-1001.0.13.3 Swift-5.0# /Library/Developer/CommandLineTools/usr/bin/lldb /Library/Developer/KDKs/KDK_10.14.6_18G2016.kdk/System/Library/Kernels/kernel(lldb) target create /Library/Developer/KDKs/KDK_10.14.6_18G2016.kdk/System/Library/Kernels/kernelLoading kernel debugging from /Library/Developer/KDKs/KDK_10.14.6_18G2016.kdk/System/Library/Kernels/kernel.dSYM/Contents/Resources/Python/kernel.pyLLDB version lldb-1001.0.13.3 Swift-5.0settings set target.process.python-os-plugin-path /Libr

[quote='767800021, EdwardD20, /thread/767800, /profile/EdwardD20'] And it says: fg: no current job [/quote] You're on the right path, and the commands you provided above look correct to my eye, short of verifying the actual addresses you're passing in from your crash report. I've never seen that specific error text before. It sounds like that could be a shell-level error, such as if you've customized Terminal beyond the basics. Is there anything like that in play for you? One other way to symbolicate the crash report that is helpful is this command: xcrun crashlog /path/to/crash.ips This runs LLDB to locate the matching dSYM file automatically on macOS and then output the symbolicated crash report, including breaking apart any inlined code in a way that atos won't do without using an -i argument in the command. — Ed Ford,  DTS Engineer