“LLDB crash”

Sorrry, that was wrong.Now I write there Main, without storyboard.And I become this error:2015-08-22 10:37:15.331 Kapitel2[1352:62128] [+] <ViewController: 0x79c22120>.writeLog:(lldb)

I've found this too - using XCode 14.3 with an iOS 16.4 simulator, and a real iPhone 13 mini on iOS 16.6, both set to UK region with a metric measurement system. let distance = Measurement(value: 22855.54, unit: .meters) Text(distance, format: .measurement(width: .wide, usage: .road)) formats as 14 miles. In the XCode debugger at a breakpoint where the Text is constructed: (lldb) p String((distance)) (String) $R0 = 22855.54 m (lldb) p Locale.current.measurementSystem (Foundation.Locale.MeasurementSystem) $R1 = (_identifier = metric, _normalizedIdentifier = metric)

Meanwhile, in this case, the stack trace of the crashed thread generated by Apple CrashReporter is also incorrect. The test code is as follows: #import int main(int argc, const char * argv[]) { dispatch_async(dispatch_get_global_queue(0, 0), ^{ raise(SIGABRT); }); printf(Test); [[NSRunLoop mainRunLoop] run]; return 0; } Crash log gen by Apple CrashReporter: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: CrashTestMac [32830] Thread 0 Crashed: 0 libdispatch.dylib 0x195ef99ac 0x195ef5000 + 18860 1 CoreFoundation 0x1961226f0 0x19611d000 + 22256 2 CoreFoundation 0x19615b5a4 0x19611d000 + 255396 3 CoreFoundation 0x19615b4f4 0x19611d000 + 255220 4 CoreFoundation 0x19615c69c 0x19611d000 + 259740 5 CoreFoundation 0x19615c46c 0x19611d000 + 259180 6 CoreFoundation 0x19626bd34 0x19611d000 + 1371444 7 libdispatch.dylib 0x195f1085c 0x195ef5000 + 112732 8 libdispatch.dylib

On that referenced thread you wrote: Adding -- between lldb and the command to debug solved the problem. Cool! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Okay, some spelunking here. Be prepared for a brain dump.I put a List into the MasterView above, so you can jump to the detail view from five rows of the list or from the button in the nav bar.Going from the row, the resulting hierarchy appears to contain two UINavigationControllers:UIHostingController ⎣ _UIHostingView ⎣ PlatformViewHost<platformviewcontrollerrepresentableadaptor<bridgedsplitview<element, group<_conditionalcontent<element,= _unaryviewadaptor<emptyview=>>>>>> ⎣ NotificationSendingSplitViewController ⎣ _UISplitViewControllerPanelImplView ⎣ _UIPanelControllerContentView ⎣ UINavigationController ⎣ UILayoutContainerView ⎣ UINavigationTransitionView ⎣ UIViewControllerWrapperView ⎣ UINavigationController ⎣ UILayoutContainerView ⎣ UINavigationTransitionView ⎣ UIViewControllerWrapperView ⎣ DestinationHostingController ⎣ _UIHostingViewYou can see them on lines 7 and 11, both with the usual UILayoutContainerView, UINavigationTransitionView, and UIViewControllerWrapper

Receiving the same error in XCode Version 8.2.1 (8C1002).If any one has found a solution to this, Please reply!expression produced error: /var/folders/6x/zkx6q8_x0nb7tngb6f8dtb300000gp/T/lldb/2531/expr14.swift:1:53: error: 'XCUIElement' is not a member type of 'XCTest'$__lldb__DumpForDebugger(Swift.UnsafePointer<XCTest.XCUIElement>(bitPattern: 0x11cd576e0).memory) ~~~~~~ ^/var/folders/6x/zkx6q8_x0nb7tngb6f8dtb300000gp/T/lldb/2531/expr14.swift:1:45: note: while parsing this '<' as a type parameter bracket$__lldb__DumpForDebugger(Swift.UnsafePointer<XCTest.XCUIElement>(bitPattern: 0x11cd576e0).memory)

Bah, I was hoping we could debug this with static analysis. Sadly, that doesn’t seem to be the case. One thing that might help here is to set a symbolic breakpoint on INIT_Processes. If you do that and then run your program, does it stop at the breakpoint? If so, what does the backtrace look like? For example, here’s what I see when I start a standard app with that breakpoint: % lldb Test777284.app/Contents/MacOS/Test777284 (lldb) target create Test777284.app/Contents/MacOS/Test777284 … (lldb) br set -n INIT_Processes Breakpoint 1: where = HIServices`INIT_Processes(), address = 0x0000000186fe371c (lldb) r … Process 28979 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1 frame #0: 0x000000018c45371c HIServices`INIT_Processes() HIServices`INIT_Processes: -> 0x18c45371c <+0>: pacibsp 0x18c453720 <+4>: stp x20, x19, [sp, #-0x20]! 0x18c453724 <+8>: stp x29, x30, [sp, #0x10] 0x18c453728 <+12>: add x29, sp, #0x10 Target 0

Yeah, that's what I've been doing. That, or sometimes defining global symbols to copy values into works as well. I'd love to be able to just tell lldb, Here's your freaking frame pointer!, though...

Hey @eskimo I'm facing the same issue that at some point Tasks are not executing anymore and here is my full stack if you could help check what's causing it to stuck: (lldb) thread backtrace all

Our team found working solution: Run in Terminal nano ~/.lldbinit Type and save: settings set target.experimental.swift-enable-cxx-interop false Restart lldb-rpc-server process

This issue is a dup of https://developer.apple.com/forums/thread/770289?answerId=853752022#853752022 and is a fundamental limitation of how XCode uses/includes clang and LLDB and how they are not backward compatible with earlier versions.

I don’t have time to review all the context from that talk but I believe there are two issues in play. First, the formatter for NSRect, which should just work. For example, if r is an NSRect local variable: (lldb) p r (NSRect) $0 = (origin = (x = 0, y = 0), size = (width = 0, height = 0))Next, calling NSMakeRect itself, which is tricky because it’s typically inlined. For that you need to import the Cocoa frameworks: (lldb) expr Enter expressions, then terminate with an empty line to evaluate: 1 @import Cocoa; 2 (lldb) p NSMakeRect(0, 0, 10, 10) (NSRect) $0 = (origin = (x = 0, y = 0), size = (width = 10, height = 10))Both of the above were done using Xcode 7.2 or OS X 10.11.2.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com