Search results for

“LLDB crash”

30,527 results found

Post

Replies

Boosts

Views

Activity

Reply to CloudKit CKQuery has stopped working
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.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Feb ’17
Reply to showallkexts fails with AttributeError 'MemMachO' has no attribute 'allow_unknown_load_commands'
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
Topic: App & System Services SubTopic: Core OS
Nov ’24
Reply to xcode pauses execution with SIGCONT
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jan ’20
Reply to Crash: IndexPath.section.getter + 168
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
Topic: UI Frameworks SubTopic: UIKit Tags:
Oct ’20
Reply to 'XCUIElement' is not a member type of 'XCTest'
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) ^
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Oct ’16
Reply to NSDistributedNotificationCenter observer spontaneously stop observing
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
Topic: Programming Languages SubTopic: General Tags:
Feb ’18
Crash log said crash on main function??
Hi,I got several crash log from organizer's crashs report.But most of them show I crash at main function like this:Thread 0GraphicService GSEventRunModalUIKit UIApplicationMainMyApplication mainlibdyld.dylib startthe crash just stop at UIApplicationMain.int main(int argc, char *argv[]){ @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([MyAppDelegate class])); }}Is there any hint that I can find out what happened?Does anybody know what may happened?Thank you~~Any response is appricated.Eric
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
327
Nov ’15
FBSSceneSnapshotRequestHandle crash
Hello, I have an App on the App Store, and today, while inspecting the App analytics on the App Store portal, I've noticed that there had been 8 crashes on the App on January 15th. I went to Firebase Crashlytics, since I used to also see the crashes on the App, and it says that there are no crashes. Then I went to Xcode to see the details of the crash, and I found this: What does this crash mean? I have no idea whatsoever. I tested the App several times, and it works perfectly. I have absolutely no idea of what this crash is. Could someone give some hints on what this crash could possibly be? Thanks.
Topic: Programming Languages SubTopic: Swift Tags:
2
0
1.8k
Jan ’22
[NSNotificationCenter postNotificationName:object:userInfo:] () crash
I am seeing this crash (log at the bottom) after I am doing playing audio with AVAudioEngine. I know it might be related to the notification observer been released without calling removeObserver first. I have reviewed my code to make sure that removeObserver is called in the dealloc method. But to be sure, I have comment out adding all the observers that listens to any notification from the Audio engine but I am still getting this crash. It is much easier to reproduce if I use a bluetooth headphone. Any suggestions on how to debug this issue? I tried to printout the notification name with po $arg1 ($arg2, or $arg3) but I get this error on the console (lldb) po $arg1error: Couldn't materialize: couldn't read the value of register x0Errored out in Execute, couldn't PrepareToExecuteJITExpressionThread 4Queue : engine (serial)#0 0x000000019a4c1bd0 in objc_msgSend ()#1 0x0000000185e123a4 in +[NSConcreteNotification newTempNotificationWithName:object:userInfo:] ()#2 0x0000000185e122e0 in
Topic: Media Technologies SubTopic: Audio Tags:
0
0
1.3k
Oct ’15
Unnamed_Symbol Crash
Experience a hard crash that I can easily replicate when selecting a specific Navigation Link that is contained in a List on the Sidebar of my Navigation split view. I can replicate the crash with no issues, but I am unacle to identify the cause. What does this crash mean? How can I find the mine of code that is causing the crash? myDashboard 11-14-22, 3-25 PM 2.crash
Topic: UI Frameworks SubTopic: SwiftUI Tags:
0
0
623
Nov ’22
crash
I am getting an app that crashes when tested when installed using TestFlight but not when tested using Xcode. Anyone have any suggestions for me?
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
0
Boosts
0
Views
242
Activity
Sep ’16
Reply to CloudKit CKQuery has stopped working
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.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
Boosts
Views
Activity
Feb ’17
Reply to showallkexts fails with AttributeError 'MemMachO' has no attribute 'allow_unknown_load_commands'
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
Topic: App & System Services SubTopic: Core OS
Replies
Boosts
Views
Activity
Nov ’24
Reply to xcode pauses execution with SIGCONT
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jan ’20
Reply to Crash: IndexPath.section.getter + 168
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
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Oct ’20
Reply to 'XCUIElement' is not a member type of 'XCTest'
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) ^
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Oct ’16
Reply to NSDistributedNotificationCenter observer spontaneously stop observing
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
Topic: Programming Languages SubTopic: General Tags:
Replies
Boosts
Views
Activity
Feb ’18
Crash log said crash on main function??
Hi,I got several crash log from organizer's crashs report.But most of them show I crash at main function like this:Thread 0GraphicService GSEventRunModalUIKit UIApplicationMainMyApplication mainlibdyld.dylib startthe crash just stop at UIApplicationMain.int main(int argc, char *argv[]){ @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([MyAppDelegate class])); }}Is there any hint that I can find out what happened?Does anybody know what may happened?Thank you~~Any response is appricated.Eric
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
2
Boosts
0
Views
327
Activity
Nov ’15
Reply to LLDB plugin fails to load on new XCode - apparent library validation issues
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
May ’23
Reply to Cannot debug app-extension-safe frameworks in main app
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?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jun ’25
Reported Crash with Analytics But Unable to View the Crash Report
There was a recent crash of my app reported in analytics but I can't see that crash report through Xcode. Does analytics report crashes even if you can't actually see the crash report?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
0
Boosts
0
Views
433
Activity
Jul ’16
FBSSceneSnapshotRequestHandle crash
Hello, I have an App on the App Store, and today, while inspecting the App analytics on the App Store portal, I've noticed that there had been 8 crashes on the App on January 15th. I went to Firebase Crashlytics, since I used to also see the crashes on the App, and it says that there are no crashes. Then I went to Xcode to see the details of the crash, and I found this: What does this crash mean? I have no idea whatsoever. I tested the App several times, and it works perfectly. I have absolutely no idea of what this crash is. Could someone give some hints on what this crash could possibly be? Thanks.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
2
Boosts
0
Views
1.8k
Activity
Jan ’22
Crash on com.apple.network.connections
Hi, We've develop and publish an application for iOS. We use firebase crashlytics to grab crash report. We get a crash that related to iOS CFNetwork. This crash happen on iPhone 14 Pro/ iOS 16.1.0 I attach the crash log below. Please check and give me some suggestion. Thank you so much. Crash Log
Topic: App & System Services SubTopic: Networking Tags:
Replies
2
Boosts
0
Views
1.1k
Activity
Nov ’22
[NSNotificationCenter postNotificationName:object:userInfo:] () crash
I am seeing this crash (log at the bottom) after I am doing playing audio with AVAudioEngine. I know it might be related to the notification observer been released without calling removeObserver first. I have reviewed my code to make sure that removeObserver is called in the dealloc method. But to be sure, I have comment out adding all the observers that listens to any notification from the Audio engine but I am still getting this crash. It is much easier to reproduce if I use a bluetooth headphone. Any suggestions on how to debug this issue? I tried to printout the notification name with po $arg1 ($arg2, or $arg3) but I get this error on the console (lldb) po $arg1error: Couldn't materialize: couldn't read the value of register x0Errored out in Execute, couldn't PrepareToExecuteJITExpressionThread 4Queue : engine (serial)#0 0x000000019a4c1bd0 in objc_msgSend ()#1 0x0000000185e123a4 in +[NSConcreteNotification newTempNotificationWithName:object:userInfo:] ()#2 0x0000000185e122e0 in
Topic: Media Technologies SubTopic: Audio Tags:
Replies
0
Boosts
0
Views
1.3k
Activity
Oct ’15
Unnamed_Symbol Crash
Experience a hard crash that I can easily replicate when selecting a specific Navigation Link that is contained in a List on the Sidebar of my Navigation split view. I can replicate the crash with no issues, but I am unacle to identify the cause. What does this crash mean? How can I find the mine of code that is causing the crash? myDashboard 11-14-22, 3-25 PM 2.crash
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
0
Boosts
0
Views
623
Activity
Nov ’22