“LLDB crash”

Works for me ¯_(ツ)_/¯. LLDB should be able to attach to LLDB, what error are you getting?

Yes, I've noticed the same issue with Xcode 12 beta 2. The break point works, but when I query objects using po, no response is returned. (lldb) po self (lldb) po datePickerView (lldb)

I’m going to recommend that you do what that message tells you, that is, file a bug with the crash report. I’m not entirely sure what’s going on here, but the backtrace of the crash thread indicates that LLDB is having problems demangling Swift symbols, and that should never crash.Please post your bug number, just for the record.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

This is error log from Xcode libc++abi: terminating due to uncaught exception of type NSException *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil' *** First throw call stack: (0x195dee964 0x192cd1814 0x195e01650 0x19c30cebc 0x1e80b0a1c 0x1e804ceb8 0x19b691ef4 0x19b68311c 0x19b682d4c 0x2b0912864 0x19c318e2c 0x19c31b524 0x2b09122b0 0x1e80dd764 0x19c6da640 0x19c47d648 0x19cac9940 0x19b6ee48c 0x19b6edee0 0x19b9904ac 0x101ca692c 0x101ca6bd4 0x19ca9f9e8 0x19c358598 0x19c3588dc 0x19c35534c 0x19c357460 0x19cacfd64 0x19cad11c4 0x19cab3c00 0x2b08027ec 0x19b6eb454 0x19b6fa65c 0x19b6ed36c 0x19b6fb80c 0x19b6faba8 0x284a26560 0x195d91f10 0x195d91e84 0x195d6facc 0x195d466d8 0x195d45a6c 0x237885498 0x19b71b73c 0x19b6c3f80 0x1016bcef0 0x192d26e28) terminating due to uncaught exception of type NSException error: Assertion failed: (false && LLDBMemoryReader module to address map ran into pointer authentication mask!), fun

Thanks for the response. Actually, it will pause and stay paused if I break in the main View, but in a service function I have for processing data it stops for a few seconds, then continues. It's a static function in a singleton, but I don't think that would make a difference. However, I actually just noticed a couple of things: 1) the app is actually detaching and continuing, and 2) it's posting an error that I hadn't noticed before (gulp): Message from debugger: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log.... It does the same breaking at various points in a custom package I'm developing alongside the app. I'll file a bug... I guess this should go to Swift, not necessarily Apple? EDIT: Actually, I see a similar unresolved issue from August at bugs.swift.org: https://bugs.swift.

Yeah, that’s what I was expecting. If you run LLDB against that, can you execute it? % lldb /path/to/python (lldb) target create /path/to/python Current executable set to '/path/to/python' …. (lldb) r … what happens here? … Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can't examine the iPad CPU registers unless I recreate the crash myself in the debugger.The CPU registers are included in the crash report, in the Thread State section.One thing I find instructive when debugging wacky problems like this is to create a dummy app that reproduces the problem. I can then experiment in the dummy app and, once I know what I’m doing, apply those results to the crash in the real app.For example, this code produces a crash that’s very like the one you’ve reported:@interface Hack : NSObject - (void)varnishWaffles:(id)sender; @end @implementation Hack - (void)varnishWaffles:(id)sender { NSLog(@varnish request from %@, sender); } @end Hack * h = [[Hack alloc] init]; [h performSelector:@selector(varnishWaffles:) withObject:self afterDelay:0.1]; [h release]; [h release];When I run this in the debugger, I see that x1 contains the selector: (lldb) p (char *)$x1 (char *) $0 = 0x00000001000b3215 varnishWaffles:Now let’s look at that in a crash

It happens on a real device This problem occurs when I close the window without writing anything or tapping done, and other times it crashes just when I close the app I think this is the real error: 2020-12-29 13:31:50.645517+0100 Nums[2002:352091] [error] precondition failure: attribute being read has no value: 785340 AttributeGraph precondition failure: attribute being read has no value: 785340. (lldb) I also get this when I separate the iPhone from the Mac: warning: failed to set breakpoint site at 0x1a2116b1c for breakpoint -5.1: error sending the breakpoint request (lldb) @State private var saveGoal = UserDefaults.standard.string(forKey: Save)

Same issue here, I can no longer debug C/C++ code in Xcode because the LLDB RPC server crashes either right on entry or after stepping. macOS version: 26.0.1 (25A362) Xcode version: Version 26.0.1 (17A400) Needless to say that this makes all development work on macOS pretty much impossible.

dyld: Library not loaded: /usr/lib/swift/libswiftCoreGraphics.dylib Referenced from: /var/containers/Bundle/Application/B5B2939D-3DDA-457D-8F72-A79EFB417C60/xxxx.app/xxxx Reason: image not found (lldb) Version 14.0 (14A309). Error still reported Crash in the following versions: iOS 12.01 iOS 12.1.2

It looks like GameKit tries to import GamePlayKit, which crashes on dyld.dyld: Library not loaded: /System/Library/Frameworks/GameplayKit.framework/GameplayKit Referenced from: /private/var/mobile/Containers/Bundle/Application/D64C3101-F1AB-454C-8992-2D24B9499076/Pique.app/Frameworks/libswiftGameKit.dylib Reason: image not found (lldb)