LLDB crash

Ah, here's this issue.(lldb) po __sharedManager.bubingaContainer<CKContainer: 0x174164bc0; containerID=<CKContainerID: 0x174028b00; containerIdentifier=iCloud.com.rschluet.bubinga, containerEnvironment=Sandbox>>I changed the environment to Production on the dashboard. I wonder how to do the same in the app. Time for some research.

Thanks for the info. I ran those commands (here is a snip from my history: 66 xcrun python3 -m pip install --user --ignore-installed macholib 67 export PATH=.:$PATH:/Users/khampton/Library/Python/3.9/bin 68 ech $PATH 69 echo $PATH 70 xcrun python3 -m pip install --user --ignore-installed future 71 lldb 72 lldb 73 lldb /Library/Developer/KDKs/KDK_15.1_24B83.kdk/System/Library/Kernels/kernel I have only installed Xcode 16.0 (16A242d) on this volume, which is running Sequoia 15.1 - all squeaky clean I think. I was initially using a host running older software and had the same problem. That one had been used as a dev system and I would not have been surprised if the reason it had the same problem was due to the Xcode confusion you describe. But prior to the upgrade (from Sonoma) to 15.1 on my m3 MBP, I had never installed Xcode on this host volume

LLDB, and hence Xcode, has infrastructure to stop in the debugger when the process receives a signal. I’m a little surprised that this kicks in for SIGCONT, but I ran a quick test here [1] and that definitely seems to be the case. Wacky. There’s two ways you could approach this:You could try to get LLDB to stop catching the SIGCONT signal (A)You could track down who is generating these SIGCONT signals and stop them (B)Personally, I’d focus on B because getting lots of SIGCONT signals is just weird. With regards A, in my tests I found that the following prevents me stopping in the debugging when the process receives SIGCONT: (lldb) process handle -n false -s false SIGCONTWith regards B, these signals can be raised from both inside and outside of your process. For the inside case, you should do the following:(lldb) thread backtrace allto see if anything obvious shows up in any of those backtraces.For the outside case… well, that depends on what platform you’re working on. On

I'm guessing this is a full crash log since this includes the termination signal and reason, etc. Is this correct? Crash reports contain a bunch of useful info. In this case I wanted to do a couple of things, one of which was disassemble the getter to confirm my understanding of the issue: (lldb) disas -s 0x1c3841820 -c 12 libswiftUIKit.dylib`merged (extension in UIKit):Foundation.IndexPath.section.getter : Swift.Int:>t0x1c3841820 <+0>:tstpttx20, x19, [sp, #-0x20]! tt0x1c3841824 <+4>:tstpttx29, x30, [sp, #0x10] tt0x1c3841828 <+8>:taddttx29, sp, #0x10tttttt; =0x10 tt0x1c384182c <+12>: movttx19, x0 tt0x1c3841830 <+16>: bltt 0x1c360819cttttttt ; Foundation.IndexPath.count.getter : Swift.Int tt0x1c3841834 <+20>: cmpttx0, #0x2ttttttttt; =0x2 tt0x1c3841838 <+24>: b.net 0x1c384184cttttttt ; <+44> tt0x1c384183c <+28>: movttx0, x19 tt0x1c3841840 <+32>: ldpttx29, x30, [sp, #0x10] tt0x1c3841844 <+36>: ldpttx20, x19, [sp], #0x

I got the same problem in my automation test. I am using the xcode version 8.0(8A218a)I always get the error as below and the object that be printed by debugdescription could not be access through codexpression produced error: /var/folders/g5/wwmlnjw90432hmd_fls8q0fdwqlkkf/T/lldb/1342/expr30.swift:1:53: error: 'XCUIApplication' is not a member type of 'XCTest'$__lldb__DumpForDebugger(Swift.UnsafePointer<XCTest.XCUIApplication>(bitPattern: 0x104d88890).memory) ~~~~~~ ^/var/folders/g5/wwmlnjw90432hmd_fls8q0fdwqlkkf/T/lldb/1342/expr30.swift:1:45: note: while parsing this '<' as a type parameter bracket$__lldb__DumpForDebugger(Swift.UnsafePointer<XCTest.XCUIApplication>(bitPattern: 0x104d88890).memory) ^

I’m not sure what’s going on here but I wanted to point out that the various notification centres have a really useful implementation of debugDescription. Obviously you can access this from LLDB: (lldb) po [[NSDistributedNotificationCenter defaultCenter] debugDescription] <_NSLocalNotificationCenter:0x6040000c09a0> Name, Object, Observer, Options … lots of good stuff …but you can also access it programmatically. Thus you could add a debugging option to your app to help with this investigation.Also, it wasn’t clear what platform you’re working on here. I suspect macOS, but please confirm.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The .NET Runtime has shipped an lldb extension Are you working on that? Or just trying to use that? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If you can reproduce this, could you add log enable lldb types -v -f /tmp/types.log to ~/.lldbinit-Xcode, restart Xcode, and reproduce the issue and then file a feedback with the /tmp/types.log log file?

i try to unwrapcuentita.cubitoCHocolate = Int(chocolate.text!) ?? 0but it crash the appand this error appears in the console2018-05-09 14:48:22.123528-0500 venta[4355:2000820] -[venta.items continuar:]: unrecognized selector sent to instance 0x155d428f02018-05-09 14:48:22.127562-0500 venta[4355:2000820] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[venta.items continuar:]: unrecognized selector sent to instance 0x155d428f0'*** First throw call stack:(0x184296d8c 0x1834505ec 0x1842a4098 0x18e34ade4 0x18429c5c8 0x18418241c 0x18dfc66c8 0x18e0e78a4 0x18dfcc77c 0x18e1021dc 0x18e5a7dd8 0x18e5a4b50 0x18423e910 0x18423c238 0x18423c884 0x18415cda8 0x18613f020 0x18e13d78c 0x1045fd02c 0x183bedfc0)libc++abi.dylib: terminating with uncaught exception of type NSException(lldb)

I am on Xcode 12.4 and also having this problem with my Flutter project. Earlier today it was opening fine, then I quit Xcode, built a new ios version of the app through VS terminal, then tried to reopen my project in Xcode but nothing happens when I click on the .xcworkspace file, it doesn't open anything. It does open other projects successfully, but still not the one above. After restarting Mac and trying again, it still does not open, but gave me the message: Xcode quit unexpectedly Process: Xcode [2379] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 12.4 (17801) Build Info: IDEFrameworks-17801000000000000~7 (12D4e) App Item ID: 497799835 App External ID: 839994694 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Xcode [2379] User ID: 501 Date/Time: 2021-04-02 18:33:36.412 +0100 OS Version: Mac OS X 10.15.7 (19H2) Report Version: 12 Bridge OS Version: 4.6 (17P6610) Anonymous UUID: 539C0A09-D3B8-3B12-BC86-25902B07D97B Tim