LLDB crash

(lldb) po retails { item_id = 43; qty = 11; } (lldb) po [retails setObject:@(self.eventID) forKey:(id)@event_id]; error: Execution was interrupted, reason: internal ObjC exception breakpoint(-4).. The process has been returned to the state before expression evaluation. (lldb) po [retails objectForKey:(id)@event_id] nil (lldb)Thank you for the help. It is odd issue. I will debug more.

Just for your happiness: adding my similar issue but with a different kit (StoreKit) and in lldb. (lldb) po product error: expression failed to parse: error: Couldn't lookup symbols: type metadata accessor for StoreKit.Product (lldb) po product.subscription error: expression failed to parse: error: Couldn't lookup symbols: StoreKit.Product.subscription.getter : Swift.Optional (lldb) po product.subscription?.promotionalOffers error: expression failed to parse: error: Couldn't lookup symbols: StoreKit.Product.subscription.getter : Swift.Optional

I've been playing around with this more and noticed that I only see the hitch when I'm running my application with the LLDB debugger connected. If I run my app standalone, it seems to work without a hitch. Could LLDB be interfering with NSEvent dispatch somehow? Is LLDB doing its own processing on my key events before it reaches my app?

I tested my app via TestFlight, and it does not open, so I'm not very optimistic Just to be clear, the TestFlight release of your app is not launching? If so, that’s something I can help you debug. Moreover, it’s important to debug this because it’s very likely that your final App Store release will behave exactly like your TestFlight release (if it doesn’t, that’s a bug on Apple’s part). When you try to launch your TestFlight release from the Finder, what happens? Does it start at all? Does it display a “you do not have permission to open” alert? Or a “quit unexpectedly” alert? Or does it hang on launch, bouncing forever in the Dock? Or start launching but then simple quit with no alerts? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi Quinn, The image list is a good suggestion. I was just using that other day. I'll try that, and see what lldb reports. This is pure C++, no Swift or ObjC usage. For some of our users, the dylib hotloads and for others not. It's a mix of people mostly on 10.15.7 and XCode 12.2/3. I did the implementation mentioned above of renaming the lib, but it seems like we have a partial reload. So some code hotloads fine, and other code is still pointing to the old lib. Some code at init of the dylib where we crash (with renaming) is reporting the previous numbered dylib in the debugger. This may be an artifact of how Xcode loads the sources once at launch, but when I do hotload, my breakpoints show the new sources. By ODR, do you mean on-demand-resource? We did have those a while back, but I think they're disabled currently. it’s definitely not there after dlclose() on my system. But my system works. Others don't. So I'll get some more info on the machines that don't hotload. after dlopen() (lldb

I generally run a command with arguments using r: % lldb Test773781 (lldb) target create Test773781 ; (lldb) r arg1 #arg2 arg3 ; 0 …/Test773781 1 arg1 The interesting thing here is that LLDB has the right arguments: (lldb) settings show target.run-args target.run-args (arguments) = [0]: arg1 [1]: #arg2 [2]: arg3 It’s just not applying them at launch. Notably, the r command is an alias for process launch: (lldb) help r Launch the executable in the debugger. Syntax: r [] r [] 'r' is an abbreviation for 'process launch -X true --' Note that -X option. Its long name is --shell-expand-args. If you set it to false, it resolves this issue: (lldb) process launch -X false … 0 …/Test773781 1 arg1 2 #arg2 3 arg3 So it seems that LLDB’s shell-like argument expansion is interpreting the # as a comment. Fun times! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

LLDB is the debugger underlying the Xcode debugger. The .lldbinit file is read by the debugger when it starts up. You can use it to customise the debugger. For example: % cat .lldbinit command alias btall thread backtrace all % lldb (lldb) help btall … 'btall' is an abbreviation for 'thread backtrace all' To learn more about how this works, see the lldb man page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the post, it seems like you are running a beta version of macOS. Can you please post the crash report from lldb? With that file, may I ask you to submit a bug? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

I am experiencing this exact issue too, and have tried almost all the suggested in the OP post to no avail.I have tried resintalling the WWDR cert and that does not help. I have also tried installing all the intermediate certs from Apple at http://www.apple.com/certificateauthority/Keychain Access evaluation of my developer cert for code signing passes.Performing the step- Set Embedded Content Contains Swift to YES (http://stackoverflow.com/questions/24002836/dyld-library-not-loaded-rpath-libswift-stdlib-core-dylib) does change the nature of the crash. After doing that, the crash output is just a non-informative (lldb) -- but typing bt after it yields:(lldb) bt* thread #1, stop reason = signal SIGABRT * frame #0: 0x0000000104e66f1c dyld`__abort_with_payload + 8 frame #1: 0x0000000104e666f4 dyld`abort_with_payload_wrapper_internal + 100 frame #2: 0x0000000104e66720 dyld`abort_with_payload + 12 frame #3: 0x0000000104e3c498 dyld`dyld::halt(char const*) + 312 frame #4: 0x000000

if you attach to a process, the lldb not link the stderr and stdout, and the stdout stderr to link system logs db. you need close the tty stderr and stdout, then open a lldb tty