Search results for

“LLDB crash”

30,527 results found

Post

Replies

Boosts

Views

Activity

App on TestFlight crashes, but no Crash Report is being recorded
tldr: Our app is randomly crashing on startup (about 1 every 10 times) but no Crash Report alert is being shown on screen nor sent to the Crash Logs tab on TestFlight. The app just simply opens and immediately closes with no apparent reason. No logs of the crash are kept inside Settings -> Privacy -> Analytics & Improvements -> Analytics Data. On the iPhone, the options Share iPhone Analytics and Share With App Developers are checked ( Settings -> Privacy -> Analytics & Improvements). No memory leaks detected using the Instruments app. More detailed explanation: Out of 6 iPhones used for testing, only 1 iPhone is presenting the crash. It's an iPhone 11 iOS 15.4 and no one has been able to replicate the crash using the other iPhones. We have an iPhone SE (2020) and an iPhone 12 Pro Max both with iOS 15.4, but we haven't been able to replicate the bug. The steps to reproduce the bug are these: Open the app, switch views, then force-clo
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
3.7k
Mar ’22
Any project I create with Xcode crashes with debugging on a physical device
Hello so when I start xcode and create a new Swift project for IOS, the project is created correctly, then when I debug on the physical device (in this case iphone 6) the application crashes! and it generates the error below! The strange thing is that in the output only writes (lldb) without a specific error, how can I solve this?Xcode Crash Image: https://imgur.com/a/mXSeLbMAll Output Error :dyld`__abort_with_payload:0x1008322f0 <+0>: mov x16, #0x2090x1008322f4 <+4>: svc #0x80-> Thread 1: signal SIGABRT 0x1008322f8 <+8>: b.lo 0x100832310 ; <+32>0x1008322fc <+12>: stp x29, x30, [sp, #-0x10]!0x100832300 <+16>: mov x29, sp0x100832304 <+20>: bl 0x100831990 ; cerror_nocancel0x100832308 <+24>: mov sp, x290x10083230c <+28>: ldp x29, x30, [sp], #0x100x100832310 <+32>: ret(lldb)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
917
Jul ’18
Reply to A static lib/framework with dwarf info. Will leaking your private info?
It’s not clear to me whether you’re trying to: Keep things secret Allow clients of your static library to debug There’s a significant tension between these two; you can’t support debugging and keep everything secret. Anyway, lemme start with the debugging situation. You are correct that: The compiler encodes a bunch of full paths into DWARF debugging information. If these paths don’t resolve, LLDB will have problems. An easy way around this is to set up source path mappings. To learn more about this, consult the LLDB help: (lldb) apropos target.source-map However, this is not your only option. For example: Various compilers have various options to cause them to embed relative paths. Or you can build your shipping libraries on a build server that uses a standard non-private path. There’s a whole world of info about this stuff out there on the ’net. A good search term is reproducible builds. In fact, one of my colleagues was has been discussing this with another developer recently in
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Mar ’25
Reply to Sequoia, multicast and lldb - no route to host
I know about this entitlement, I've been using it for a while for multiple apps, but then why does it work without lldb or any entitlements? This is why it doesn't make much sense. If the entitlement is required, then I should be getting no route to host without lldb, which is not the case. What I didn't try is to debug a binary with entitlements appiled, however it'd be very unreasonable to expect debug binaries to be signed which is a requirement to apply entitlements. I'm just trying to debug locally, on my own machine, these binaries are built on the same machine, never distributed, same as debugging through Xcode, which I can't because this is not an Xcode project. For distribution it's 100% sensible, but I don't think the entitlement has anything to do with it.
Topic: App & System Services SubTopic: Networking Tags:
Sep ’24
Crash logs disappered "No crash logs"
Since XCode 13.1 I'm getting no crash logs error in my Organizer window. I have re-authenticated, changed the filters to be as broad as possible (ie all versions, all platforms, for the last year) - and I still get this error. I know there are crash logs because up until now (ie the past few weeks) I've been reviewing them! I've cleared derived data, I've cleaned the project, I've rebooted, I've closed and restarted xCode, I've opened XCode preferences and re-authenticated (I had recently changed password so it was prompting me to re-authenticate anyway). Still, no crash logs. Any other cached data I should be clearing that could fix this? I know I have crash logs piling up right now.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
1k
Jul ’22
Reply to Exception reason in Xcode Organizer
The crash report is attached. Oh, that’s very enlightening. Consider the backtrace of the crashing thread: 0 CoreFoundation … __exceptionPreprocess + 220 … 1 libobjc.A.dylib … objc_exception_throw + 60 … 2 Foundation … _writeJSONNumber + 1244 … 3 Foundation … ___writeJSONObject_block_invoke + 388 … 4 CoreFoundation … __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 … 5 CoreFoundation … -[__NSDictionaryI enumerateKeysAndObjectsWithOptions:usingBlock:] + 184 … 6 Foundation … _writeJSONObject + 508 … 7 Foundation … ___writeJSONArray_block_invoke + 260 … 8 CoreFoundation … __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 … 9 CoreFoundation … -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 196 … 10 Foundation … _writeJSONArray + 340 … 11 Foundation … ___writeJSONObject_block_invoke + 388 … 12 CoreFoundation … __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 … 13 CoreFoundation … -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 208 … 14 Foundation … _writeJSONObject + 508 … 15 F
Topic: App & System Services SubTopic: General Tags:
Dec ’21
Crash in NetConnection::dequeue When Spawning URLSessionTasks in Loop
I'm encountering a null pointer dereference crash pointing to the internals of CFNetwork library code on iOS. I'm spawning URLSessionTasks at a decently fast rate (~1-5 per second), with the goal being to generate application layer network traffic. I can reliably encounter this crash pointing to NetConnection::dequeue right after a new task has been spawned and had the resume method called. I suspect that this is perhaps a race condition or some delegate/session object lifecycle bug. The crash appears to be more easily reproduced with a higher rate of spawning URLSessionTasks. I've included the JSON crash file, the lldb stack trace, and the source code of my URLSession(Task) usage. urlsession_stuff_stacktrace.txt urlsession_stuff_source.txt urlsession_crash_report.txt
Topic: App & System Services SubTopic: Networking Tags:
1
0
37
17h
Crash on iOS 13 simulator causes crash reporter to crash on Monterey
We’ve run into a strange issue here. We are running an iOS 13 simulator device on Monterey (x86_64) and an app on said device causes a crash (this is expected). However, when the crash reporter attempts to write out the crash report, it crashes. Here is an excerpt from the translated crash report: Process: ReportCrash [88409] Path: /System/Library/CoreServices/ReportCrash Identifier: ReportCrash Version: ??? Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 503 Date/Time: 2022-06-01 15:45:32.9876 -0400 OS Version: macOS 12.3.1 (21E258) Report Version: 12 Bridge OS Version: 6.4 (19P4243) Anonymous UUID: 9D02B4AF-C468-6AD7-78E4-48395612A5A9 Time Awake Since Boot: 450000 seconds System Integrity Protection: enabled Crashed Thread: 3 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000001206c2008 Exception Codes: 0x0000000000000001, 0x00000001206c2008 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Names
Topic: App & System Services SubTopic: Core OS Tags:
1
0
1k
Jun ’22
Crash from IOSSurfaceCreate
I am getting this crash log, where crash is happening from iosCreateNamedProperties. I have attached image of crash log. What could be the reason and how to solve it.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
1.1k
Activity
Apr ’23
App on TestFlight crashes, but no Crash Report is being recorded
tldr: Our app is randomly crashing on startup (about 1 every 10 times) but no Crash Report alert is being shown on screen nor sent to the Crash Logs tab on TestFlight. The app just simply opens and immediately closes with no apparent reason. No logs of the crash are kept inside Settings -> Privacy -> Analytics & Improvements -> Analytics Data. On the iPhone, the options Share iPhone Analytics and Share With App Developers are checked ( Settings -> Privacy -> Analytics & Improvements). No memory leaks detected using the Instruments app. More detailed explanation: Out of 6 iPhones used for testing, only 1 iPhone is presenting the crash. It's an iPhone 11 iOS 15.4 and no one has been able to replicate the crash using the other iPhones. We have an iPhone SE (2020) and an iPhone 12 Pro Max both with iOS 15.4, but we haven't been able to replicate the bug. The steps to reproduce the bug are these: Open the app, switch views, then force-clo
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
2
Boosts
0
Views
3.7k
Activity
Mar ’22
Xode LLDB, if the current input source is Chinese, typing 'po' will hang forever
Hi there, I already filed radar FB9958917 two weeks ago and no response. this is super annoying when you are debuging a giant app and suddenly you switch the input source, and all debug work is gone and I have to kill xcode to start over again. unacceptable, only happens after you upgrade to 13.3
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
538
Activity
Apr ’22
Crash on com.apple.CFNetwork.CustomProtocols
Recently received quite a number of crashes, and notice from the crash log it seems related to CFNetwork. In the crashed thread's stack trace, I do not see any of my application code involved. GA.crash
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
984
Activity
Jun ’22
Any project I create with Xcode crashes with debugging on a physical device
Hello so when I start xcode and create a new Swift project for IOS, the project is created correctly, then when I debug on the physical device (in this case iphone 6) the application crashes! and it generates the error below! The strange thing is that in the output only writes (lldb) without a specific error, how can I solve this?Xcode Crash Image: https://imgur.com/a/mXSeLbMAll Output Error :dyld`__abort_with_payload:0x1008322f0 <+0>: mov x16, #0x2090x1008322f4 <+4>: svc #0x80-> Thread 1: signal SIGABRT 0x1008322f8 <+8>: b.lo 0x100832310 ; <+32>0x1008322fc <+12>: stp x29, x30, [sp, #-0x10]!0x100832300 <+16>: mov x29, sp0x100832304 <+20>: bl 0x100831990 ; cerror_nocancel0x100832308 <+24>: mov sp, x290x10083230c <+28>: ldp x29, x30, [sp], #0x100x100832310 <+32>: ret(lldb)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
2
Boosts
0
Views
917
Activity
Jul ’18
WidgetKit crash
This is a general question- When a WidgetKit extension crashes is it ever restarted? When my widgets crash they do not refresh until the device is rebooted.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
623
Activity
Jan ’21
Reply to A static lib/framework with dwarf info. Will leaking your private info?
It’s not clear to me whether you’re trying to: Keep things secret Allow clients of your static library to debug There’s a significant tension between these two; you can’t support debugging and keep everything secret. Anyway, lemme start with the debugging situation. You are correct that: The compiler encodes a bunch of full paths into DWARF debugging information. If these paths don’t resolve, LLDB will have problems. An easy way around this is to set up source path mappings. To learn more about this, consult the LLDB help: (lldb) apropos target.source-map However, this is not your only option. For example: Various compilers have various options to cause them to embed relative paths. Or you can build your shipping libraries on a build server that uses a standard non-private path. There’s a whole world of info about this stuff out there on the ’net. A good search term is reproducible builds. In fact, one of my colleagues was has been discussing this with another developer recently in
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Mar ’25
Reply to Sequoia, multicast and lldb - no route to host
I know about this entitlement, I've been using it for a while for multiple apps, but then why does it work without lldb or any entitlements? This is why it doesn't make much sense. If the entitlement is required, then I should be getting no route to host without lldb, which is not the case. What I didn't try is to debug a binary with entitlements appiled, however it'd be very unreasonable to expect debug binaries to be signed which is a requirement to apply entitlements. I'm just trying to debug locally, on my own machine, these binaries are built on the same machine, never distributed, same as debugging through Xcode, which I can't because this is not an Xcode project. For distribution it's 100% sensible, but I don't think the entitlement has anything to do with it.
Topic: App & System Services SubTopic: Networking Tags:
Replies
Boosts
Views
Activity
Sep ’24
Crash logs disappered "No crash logs"
Since XCode 13.1 I'm getting no crash logs error in my Organizer window. I have re-authenticated, changed the filters to be as broad as possible (ie all versions, all platforms, for the last year) - and I still get this error. I know there are crash logs because up until now (ie the past few weeks) I've been reviewing them! I've cleared derived data, I've cleaned the project, I've rebooted, I've closed and restarted xCode, I've opened XCode preferences and re-authenticated (I had recently changed password so it was prompting me to re-authenticate anyway). Still, no crash logs. Any other cached data I should be clearing that could fix this? I know I have crash logs piling up right now.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
3
Boosts
0
Views
1k
Activity
Jul ’22
Crash in TrafficLights
Recently, there are some strange crash in my app，the crash stack appears TrafficLights and ExcursionTrain, but I do not search any results in my project.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
0
Boosts
0
Views
418
Activity
Feb ’24
accessory crash
hi want to ask im buying iph 12 in november 2020 and there accessory crash , can i use my guarantee because accessory crash ?
Topic: App & System Services SubTopic: Hardware Tags:
Replies
0
Boosts
0
Views
845
Activity
Feb ’21
Reply to Exception reason in Xcode Organizer
The crash report is attached. Oh, that’s very enlightening. Consider the backtrace of the crashing thread: 0 CoreFoundation … __exceptionPreprocess + 220 … 1 libobjc.A.dylib … objc_exception_throw + 60 … 2 Foundation … _writeJSONNumber + 1244 … 3 Foundation … ___writeJSONObject_block_invoke + 388 … 4 CoreFoundation … __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 … 5 CoreFoundation … -[__NSDictionaryI enumerateKeysAndObjectsWithOptions:usingBlock:] + 184 … 6 Foundation … _writeJSONObject + 508 … 7 Foundation … ___writeJSONArray_block_invoke + 260 … 8 CoreFoundation … __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 … 9 CoreFoundation … -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 196 … 10 Foundation … _writeJSONArray + 340 … 11 Foundation … ___writeJSONObject_block_invoke + 388 … 12 CoreFoundation … __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 … 13 CoreFoundation … -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 208 … 14 Foundation … _writeJSONObject + 508 … 15 F
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Dec ’21
Reply to waze shared application
Thanks for reply, I cant see anything worng at lldb. The point is, that its worked for few days and then stop. If im paste the same code (waze://?ll=32.233, 31.333&navigate=yes) to the safary url its working fine. Any idea?
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Aug ’15
Crash in NetConnection::dequeue When Spawning URLSessionTasks in Loop
I'm encountering a null pointer dereference crash pointing to the internals of CFNetwork library code on iOS. I'm spawning URLSessionTasks at a decently fast rate (~1-5 per second), with the goal being to generate application layer network traffic. I can reliably encounter this crash pointing to NetConnection::dequeue right after a new task has been spawned and had the resume method called. I suspect that this is perhaps a race condition or some delegate/session object lifecycle bug. The crash appears to be more easily reproduced with a higher rate of spawning URLSessionTasks. I've included the JSON crash file, the lldb stack trace, and the source code of my URLSession(Task) usage. urlsession_stuff_stacktrace.txt urlsession_stuff_source.txt urlsession_crash_report.txt
Topic: App & System Services SubTopic: Networking Tags:
Replies
1
Boosts
0
Views
37
Activity
17h
Crash on iOS 13 simulator causes crash reporter to crash on Monterey
We’ve run into a strange issue here. We are running an iOS 13 simulator device on Monterey (x86_64) and an app on said device causes a crash (this is expected). However, when the crash reporter attempts to write out the crash report, it crashes. Here is an excerpt from the translated crash report: Process: ReportCrash [88409] Path: /System/Library/CoreServices/ReportCrash Identifier: ReportCrash Version: ??? Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 503 Date/Time: 2022-06-01 15:45:32.9876 -0400 OS Version: macOS 12.3.1 (21E258) Report Version: 12 Bridge OS Version: 6.4 (19P4243) Anonymous UUID: 9D02B4AF-C468-6AD7-78E4-48395612A5A9 Time Awake Since Boot: 450000 seconds System Integrity Protection: enabled Crashed Thread: 3 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000001206c2008 Exception Codes: 0x0000000000000001, 0x00000001206c2008 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Names
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
1k
Activity
Jun ’22