Fix Xcode navigation for stack trace paths with leading slash#3291
Draft
tinder-hemanthprasad wants to merge 1 commit intoMobileNativeFoundation:mainfrom
Draft
Conversation
Fixes MobileNativeFoundation#3290 Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3290
Stack traces in Xcode show workspace-relative paths with a leading slash (e.g.,
/Projects/Module/File.swift:123). These paths are not clickable because the lldbinit source-map configuration only handles paths starting with./and not/.This adds a source-map entry for the
/prefix tocreate_lldbinit.sh, mapping it to the workspace root ($execution_root).Testing
~/.lldbinit-rules_xcodeproj, restarted Xcode, and confirmed clicking stack trace paths now navigates correctlyRelated
Related to #3134 (other lldbinit configuration concerns)
Made with Cursor