Post

Replies

Boosts

Views

Activity

Breakpoints not resolving on Xcode 14 (Turn to outlines when app is run)
We are running into an issue where breakpoints are not resolving on Xcode 14 (The same break points on Xcode 13.4.1 are working fine). They change to an outline when we run our app I have tried all the usual fixes Cleaned the build Cleaned Derived data Restarted Xcode Restarted the machine Re-cloned the repo to see if starting fresh helps I have also tried Removing all symbol stripping Ensuring the DSYM is getting generated and is loaded in the debugger Removing all optimization options Tried the Xcode 14.1 beta What's really strange is the break points will work occasionally and will work for a few runs and then stop working again. Does anyone have any suggestions?
4
3
3.7k
Oct ’22
Xcode 15.0 linker error (Assertion failed: (rebasePtr->target == low56), function writeChainEntry, file ChainedFixups.cpp, line 1218)
Hi! On the latest version of Xcode (15.0 released on Sept 18th, 23) we are running into a linker failure when we try to archive. The same project builds fine on Xcode 14.3.1. It also builds fine when building a debug build to device. This is the stack from the build output 0 0x1021ab648 __assert_rtn + 72 1 0x102106998 mach_o::PointerFormat_DYLD_CHAINED_PTR_64_OFFSET::unauthRebaseIsVmAddr() const + 0 2 0x102107b44 ___ZN6mach_o13ChainedFixups11buildFixupsENSt3__14spanIKNS_5Fixup10BindTargetELm18446744073709551615EEENS2_IKNS0_17SegmentFixupsInfoELm18446744073709551615EEEyRKNS0_13PointerFormatEjb_block_invoke_2 + 212 3 0x18163c440 _dispatch_client_callout2 + 20 4 0x18164ff1c _dispatch_apply_invoke + 224 5 0x18163c400 _dispatch_client_callout + 20 6 0x18164dfb8 _dispatch_root_queue_drain + 684 7 0x18164e6c0 _dispatch_worker_thread2 + 164 8 0x1817e8038 _pthread_wqthread + 228 ld: Assertion failed: (rebasePtr->target == low56), function writeChainEntry, file ChainedFixups.cpp, line 1218. clang: error: linker command failed with exit code 1 (use -v to see invocation) Any ideas on what we might be doing wrong? Is our best bet to disable the new linker and just keep checking with each new version?
1
1
931
Sep ’23