Search results | Apple Developer Forums

Reply to Please Help!!! My app crash at [UITableViewCellContentView dealloc]

I can locate the crash object, but I do not know why , do not know how to fix.it crash at :* frame #0: 0x0000000180eb9b90 libobjc.A.dylib`objc_msgSend + 16 frame #1: 0x00000001821f5934 Foundation`empty + 72 frame #2: 0x0000000182150cf8 Foundation`-[NSConcreteMapTable dealloc] + 60 frame #3: 0x0000000182198888 Foundation`-[NSISEngine dealloc] + 104 frame #4: 0x00000001869886dc UIKit`-[UIView dealloc] + 624 frame #5: 0x0000000186a8c4c0 UIKit`-[UITableViewCellContentView dealloc] + 80i print UITableViewCellContentView address and view:(lldb) register readGeneral Purpose Registers: x1 = 0x0000000187391ccc countByEnumeratingWithState:objects:count: x19 = 0x0000000128928270 x20 = 0x0000000126800048 x21 = 0x0000000126800010 x22 = 0x0000000126800000 x23 = 0x00000001a01d90e0 libsystem_pthread.dylib`_thread + 224 x24 = 0x0000000126800000 x25 = 0x00000000a1a1a1a1 x26 = 0x6000489658fc9aa6 x27 = 0x00000001a01d90e0 libsystem_pthread.dylib`_thread + 224 x28 = 0xa3a3a3a3a3a3a3a3 fp = 0x000000016fd6

Programming Languages General

Apr ’16

Reply to Crash reports downloaded by Xcode contain impossible call hierarchy

Would you mind opening an enhancement request for this, with both the crash log you have from the system and the one expanded by LLDB attached? (And please post the FB number here.) I'd like to treat this as a chance for improvement in the display of your crash log so that it was more intuitive to you what has happening. Speaking broadly and not specifically to your examples, backtraces in optimized builds sometimes are surprising because of the optimizations. That's not to say that the crash report is wrong — it is correct to the actual instructions addresses that the system called in backtrace order to the crash — but that it may have either more or fewer frames than you expect from the source code because of what the optimizations added or removed. That's why I want to be specific that the above enhancement request regards displaying the optimization info that you needed to understand what happened, and not that what the crash report recorded the wrong

Developer Tools & Services General

Mar ’25

Reply to [Resolved] App crashes when launched from dock, doesn't crash when run from terminal

[WillBProg3245 emailed me their crash report.]Well, that’s an interesting crash you’ve got there. I had a look at your crash report and it didn’t reveal anything new, so I then started poking around in your core.% lldb -c core.719 (lldb) target create --core core.719 Core file '/Users/quinn/Desktop/core.719' (x86_64) was loaded. (lldb) thread list Process 0 stopped … thread #10: … libxpc.dylib`xpc_release + 6 … … (lldb) thread select 10 … (lldb) disas -f libxpc.dylib`xpc_release: 0x7fff65659d9e <+0>: testb $0x1, %dil 0x7fff65659da2 <+4>: jne 0x7fff65659ddd ; <+63> -> 0x7fff65659da4 <+6>: movq (%rdi), %rax …As you can see, the program has crashed referencing RDI at +6. So what’s in RDI:(lldb) p/x $rdi (unsigned long) $0 = 0xe2160458f3753a00Whoah, that does not look even close to a valid pointer. Heap pointers on modern versions of macOS typically look like 0x00006000_xxxxxxxx. Moreover, all poin

Developer Tools & Services Xcode

Jan ’20

Reply to crash report _NSThreadPerformPerform

In my little test app based on your crashing test code, I was able to successfully reproduce printing out the string pointed to by the x1 register.Cool. To quote Obi-Wan, “You’ve taken your first step into a larger world.”As an aside, I also tried printing out the SEL receiver object, which is supposedly stored in register x0 at the time of the crash.That won’t work, because the receiving object is allocated from the heap and thus is found at an (essentially) random place on each run of the app.Well now what? This is in UIKit.Right, but that shouldn’t stop you (-: To start, you can explore this by modifying your test app to use a UIKit selector. For example:@interface Hack : NSObject - (void)applicationWillTerminate:(id)sender; @end @implementation Hack - (void)applicationWillTerminate:(id)sender { NSLog(@well terminate request from %@, sender); } @end Hack * h = [[Hack alloc] init]; [h performSelector:@selector(applicationWillTerminate:) withObject:self afterDelay:0.1]; [h release]; [h release];A crash

Developer Tools & Services Xcode

Nov ’16

Reply to getattrlistbulk inode

Consider this: % lldb (lldb) p/x 78133671 (int) $0 = 0x04a839a7 (lldb) p/x 1152921500311879699 (long) $1 = 0x0fffffff00000013 I’m not sure what attribute your code is fetching, but it’s definitely not an inode number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App & System Services Core OS

Feb ’22

Reply to Crash log and symbolication when using Xcode Cloud

Thank you @DTS Engineer. These are great details! I've follow-up questions to be sure using Xcode Cloud doesn't turn out in being a mistake. If I archive only using Xcode Cloud (with the option to include symbol enabled), can the Xcode Organizer show symbolicated crash logs for app builds that are more than 30 days old (the archive availability window)? For example, a crash for an app version released 6 months ago. Can you elaborate on the significant debugging capabilities using LLDB that aren't possible without them. What does that mean? Basically, what I want is to be able to see the crash logs in Xcode Organizer, and open them in Xcode Project at the commit I used to archive the app to see what caused the crash and to fix it. I hope it's clear. Thank you, Axel

Developer Tools & Services Xcode Cloud

Jun ’25

LLDB not loading all .dSYM's

I have a large application and do not have .dSYM's for all .dylibs. We have a critical component in which I have all of the .dSYM's, but I can not get XCode to load some (about 25% load) of the .dSYM's. I can manually load one .dSYM at a time using add-dsym, but that would take considerable time. I am using XCode 8.2.1 on Sierra.For example one of my .dylibs that where its .dSYM is not loaded had the following uuid : 7CB9B955-FC91-3E7C-BE63-F956F8D57D55:In terminal when I type mdfind and dwarfdump you can see that the uuid's match:mdfind com_apple_xcode_dsym_uuids == 7CB9B955-FC91-3E7C-BE63-F956F8D57D55/Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYMdlsept:~ dlsept$ xcrun dwarfdump --uuid /Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYMUUID: 7CB9B955-FC91-3E7C-BE63-F956F8D57D55 (x86_64) /Users/dlsept/main/Publish/3P/FusionCoreSymbols/osx_release_main_2.1.4950_symbols/NuBase10.dylib.dSYM/Contents/Resources

Developer Tools & Services Xcode Graphical Debugger

0

1.1k

Jun ’17

LLDB error: type for self cannot be reconstructed: type for typename

All is fine in Xcode15, no LLDB errors whatsoever, but in Xcode16 I can't get any variable displayed in the console because of the following error: error: type for self cannot be reconstructed: type for typename $....... was not found (cached) error: Couldn't realize Swift AST type of self. Hint: using `v` to directly inspect variables and fields may still work. I've checked the output of swift-healthcheck and there are several messages like this: SwiftASTContextForExpressions(module: ROA, cu: ROA+ViewLayer.swift)::LoadOneModule() -- Missing Swift module or Clang module found for UIKit, imported via SwiftDWARFImporterDelegate. Hint: Register Swift modules with the linker using -add_ast_path. I added -add_ast_path to the OTHER_LDFLAGS in the faulty module's build settings but no luck. How can I debug my project in Xcode16?

Developer Tools & Services Xcode Xcode LLDB

15

0

1.9k

Jan ’25

Xcode crashes when opening gamescene.sks

I was using xcode 7.3 and had in issue i thought will be fixed when i installed 7.3.1, but no luck.Whenever i open gameScene.sks in xcode, it crashes with the error message ''Xcode quit unexpectedly''. I tried right-clicking the file and pressing ''Open as spriteKit editor'', but it still crashes.I tried googling it, and found some posts on stackoverflow, but they had no answers to them.

Developer Tools & Services Xcode Xcode

2

0

1.1k

May ’16

Save Screen Shot crash

With the latest release of Xcode 8.2 (8C38) on El Capitan 10.11.6 attempting to Save Screen Shot (⌘S) now results in a consistent crash across projects:Simulator quit unexpectedly while using the libswiftFoundation.dylib plug-in.I'm not seeing this when running on my machine with Sierra 10.12.2, but updating this work machine with Sierra is not yet an option.Is anyone else able to reproduce this?

Developer Tools & Services Xcode Simulator

15

0

3.9k

Dec ’16

Reply to Strange problems with breakpoints appear after migration (MacBook x86_64 Sequoia to Mac M3 arm64 Sequoia)

We have tried BOTH ways (on Sequoia/arm64): without lldb, that is serveur.out with lldb, that is lldb server.out Most of the post shows the second call (with lldb). We are NOT creating an app (in the macOS sense) at the moment. We start our programs from the Terminal (Serveur on 1 window, Client on another window, both in the same machine or not -- communication is done by sockets) ==> Since then, we have tried to change from clang to another C++ compiler. Still problems with gcc The problem disappears with c++ ! We are now sure that the problem comes from the amr64 version of clang, because exactly the same code runs without problems on Sequoia/x86_64/clang.

Developer Tools & Services General

Nov ’24

Reply to SwiftUI - NavigationLink inside NavigationBarItems, returns error on navigating from detail back to master view

Hokay, let's run it again with a breakpoint on -[UINavigationController popToViewController:animated:]. We push via a list row, then pop. Interestingly, the entire animation completes before -popToViewController:animated: is invoked, as though SwiftUI is actually doing that whole thing itself—which is interesting.However, when it's done we see that method being invoked on a UINavigationController at 0x7fbd13035200, and it's being asked to pop to an instance of UIHostingController<_VariadicView_Children.Element> at 0x7fbd1782e940. The navigation controller has this to say about its content:(lldb) po [$rdi viewControllers] <__NSSingleObjectArrayI 0x60000139c6b0>( <_TtGC7SwiftUI19UIHostingControllerVVS_22_VariadicView_Children7Element_: 0x7fbd1782e940> ) (lldb)In other words, it only contains that one item—the same one to which it's being asked to pop. So it seems that the error is less likely about emptying the stack, but about asking to go back to a view that isn't in the st

UI Frameworks SwiftUI

Oct ’19

Reply to GDB equivalent of "-x" option in lldb

Yes, though lldb allows a few more options than gdb. You can provide commands to run either before or after the file provided on the command line is read in. You can also provide single lldb commands. You can provide more than one file or single command, and they will get run in the order they appear on the command line. Anyway, try running lldb --help in Terminal and you will get a full description of the various options.

Developer Tools & Services Xcode

Sep ’15

Reply to Generating JWK from EC public key x and y coordinates

That's really weird because I have the same thing with underscores in the lldb output and in this box. Looks like it is stripped if it's not inside a code block. Pasting it again here within a code block. I'm using the base64 encoder on NSData and making it URL safe as you've shown. x: EUA2cFR9ZrGJozbkwYeyBrbrG3p4ChHBQu_sWem2sgM y: n6WQz7uMkIALgLM5xriANs5VXKy_2Q71jetoI6Pzojk ==== DON'T USE THIS (BELOW) SINCE UNDERSCORES ARE STRIPPED ===== (lldb) po xbytes EUA2cFR9ZrGJozbkwYeyBrbrG3p4ChHBQusWem2sgM (lldb) po ybytes n6WQz7uMkIALgLM5xriANs5VXKy2Q71jetoI6Pzojk

Privacy & Security General

Jun ’20

Reply to Xcode needs to support natvis files

Hi, we do try to see forum posts too, but yes filing feedback is the best way to be seen, and also to know when your requests have been addressed in an Xcode release. We are aware of lldb-eval. There has been a proposal to incorporate its functionality into lldb. See https://discourse.llvm.org/t/rfc-data-inspection-language/69893 As mentioned in that forum post, lldb-eval itself doesn't support Natvis. The post mentions that some Natvis tooling exists which makes use of lldb-eval, for performance. it's far simpler to edit and write than the lldb rules and python scripting. Do you edit and write the Natvis directly with XML? Or are there high level tools for writing Natvis that hide the XML syntax? I have looked at Natvis, and found myself thinking the opposite, that it must be difficult to get over the learning curve of writing debug formatters in XML. If you send a feedback, please share its URL here. -- Dave

Developer Tools & Services Xcode

Feb ’24

LLDB crash

Post

Replies

Boosts

Views

Activity