Added normalize-path-separator option as debugging .NET on Windows 10 with netcoredbg was not registering breakpoints #273
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.
Add normalize-path-separator option for path separator normalization
Some debug adapters require exact path matching with symbol files that
may use different path separators than Emacs. This is particularly
important for netcoredbg on Windows, where PDB files contain backslash
separators but Emacs uses forward slashes.
The new normalize-path-separator configuration option allows users to
specify path separator normalization:
This ensures breakpoints can be properly verified by debug adapters
that perform strict path matching.
Fixes: Issue where netcoredbg on Windows fails to verify breakpoints
due to path separator mismatch between Emacs (/) and PDB symbols ().