Search results for

LLDB crash

29,559 results found

Post

Replies

Boosts

Views

Activity

Reply to Unable to cast NSDiffableDataSourceSnapshotReference
Also, if you try to use the NSDiffableDataSourceSnapshotReference that is passed to your delegate in controller(_, didChangeContentWith:), you get all sorts of type errors which seem to indicate a problem with how this type is imported into Swift:(lldb) po snapshot.sectionIdentifiers Precondition failed: NSArray element failed to match the Swift Array Element type Expected NSManagedObjectID but found __NSCFConstantString: … (lldb) po snapshot.itemIdentifiers Precondition failed: NSArray element failed to match the Swift Array Element type Expected NSString but found NSTemporaryObjectID_0: …This lets me think that NSDiffableDataSourceSnapshotReference<NSManagedObjectID, NSString> should probably be NSDiffableDataSourceSnapshotReference<NSString, NSManagedObjectID>.
Jun ’19
Reply to Locale.MeasurementSystem ignored by MeasurmentFormatter
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)
Topic: Programming Languages SubTopic: Swift Tags:
Jul ’23
Reply to Using raise in GCD can cause timing issues with the signal mechanism.
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
Jul ’25
Crash
Hello! I found a crash at the start of the app with an error: error: memory read failed for 0x0 Thread 1: EXC_BAD_ACCESS (code=1, address=0x0) If I add to the project: @available(iOS 16.0, *) @MainActor class SomeClass { var configuration: ImageAnalyzer.Configuration? } But if I replace the class with a structure, then the app will run without crash: @available(iOS 16.0, *) @MainActor struct SomeStruct { var configuration: ImageAnalyzer.Configuration? } Xcode 14.0 beta 5 (14A5294e) iOS 15.6 On iOS 16 beta, both options work, without crashes. Any suggestion as to what to look for?
2
0
1.8k
Aug ’22
Reply to SwiftUI - NavigationLink inside NavigationBarItems, returns error on navigating from detail back to master view
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
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Oct ’19
Reply to Service Showing "Not Responding" in Activity Monitor Despite Running Threads.
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
Apr ’25
Reply to 'XCUIElement' is not a member type of 'XCTest'
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)
Jan ’17
My app crashes but no crashes are registered in itunesconnect
Hi.I need ideas on how to bugtrack this issue:We tested our app in simulator - and it worked fine, we tested with testflight - and it worked fine (we did experience a few crashes) and then we got it approved for appstore - but now most users experience crashes on startup. My problem is that these crashes dosn't showup in the itunesconnect stats? so I'm unsure how to bugtrack it. We did see some crashes on out version 1.0 but no crashes on 1.1 - even though users reported it directly to us. We think the crash is caused by a http-lookup in our db through a php -script.2 questions:1. why dosnt the crashes showup?2. any ideas on how to bugtrack this?Thanks
0
0
251
Jan ’17
Reply to Is my copy of lldb up-to-date?
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
Jan ’16