LLDB crash

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)

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

(lldb) image lookup -a 0xffffff801a5ac283 Address: kernel[0xffffff80003ac283] (kernel.TEXT.text + 344707) Summary: kernelpanic + 99 at debug.c (lldb) image lookup -a 0xffffff801a6d91ea Address: kernel[0xffffff80004d91ea] (kernel.TEXT.text + 1577450) Summary: kernelpanic64 + 218 at trapnative.c:152 (lldb) image lookup -a 0xffffff801a55a51f Address: kernel[0xffffff800035a51f] (kernel.TEXT.text + 9503) Summary: kernelhndl_double_fault + 15 (lldb) image lookup -a 0xffffff801a6cd95f Address: kernel[0xffffff80004cd95f] (kernel.TEXT.text + 1530207) Summary: kernelusimplelock + 47 at machineroutines.c (lldb) image lookup -a 0xffffff801a5c95ad Address: kernel[0xffffff80003c95ad] (kernel.TEXT.text + 464301) Summary: kernelthread_dispatch + 445 at sched_prim.c:2768 (lldb) image lookup -a 0xffffff801a5c906e Address: kernel[0xffffff80003c906e] (kernel.TEXT.text + 462958) Summary: kernelthreadinvoke + 1710 at schedprim.c:2559 (lldb) image lookup -a 0xffffff801a

I have the same issue with lldb in my project!Both Beta 2 and 3 give meerror: Couldn't lookup symbols: __swift_FORCE_LOAD_$_swiftCoreMIDIwhen trying to execute any lldb command.This is the case only with a real device (I've tested on 12.3.1). On simulator lldb works properly.

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)

@rickbdotcomSame story here. Excluding 3rd party framework from Carthage (which was distributed as pre-compiled binary) and compiling/linking it directly within the project – does fix Xcode crash and restores lldb breakpoints functionality.Thanks!UPDATE: It is possible to force Carthage to build frameworks from sources by passing additional argument carthage update --no-use-binaries

So I found the lldb incantation to wait for a process: sudo lldb -n svn -w I then launched svn via my launchagent and indeed lldb attached to it, and indeed the launchagent waited. I waited minutes, then told lldb to continue, and it did, and then the launchagent also finished. But again svn output 'no route to host', and again no permission prompt appeared for me the whitelist svn. I also updated to macOS 15.4, which has not helped.

Based on a post i found I tried deleting ~/Library/Preferences/com.apple.dt.Xcode.plist ~/Library/Caches/com.apple.dt.Xcode Which helped in the way that I can now Run the extension like a normal app, just choosing Finder as the host app. It hits the breakpoint but the same issue as above -> crash upon stepping over or upon usage of lldb.

This is caused by Python version mismatch between LLDB and scripts inside kernel's dSYM. Python scripts inside your dSYM require Python 2 but Python 2 support has been removed from newer LLDBs. To solve the problem you will have to install older LLDB/Xcode that still has Python 2 support.

same problem here. maybe 'lldb-rpc-server' related. during the 2 minutes, 'lldb-rpc-server' take 100% CPU.