microsoft / microsoft/vscode-mono-debug
Breakpoints in files from symlinked dirs
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 180
- Forks
- 182
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
When directory /foo/src/build is a symlink to /bar/build, we open a file /foo/src/build/file.cs and place a breakpoint there - breakpoints will hit, however IDE will reopen file from /bar/build/file.cs path. VSCode thinks it is a different file and thus placed breakpoints are not visible. Debugging works otherwise.
Could this plugin use /foo/src/build/file.cs provided it is the same file that debugging info points to?
By the way - awesome plugin! Thank you 👍
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the breakpoint scenario with /foo/src/build symlinked to /bar/build, then trace how the plugin handles the source path from debugging information. Done means VS Code continues using /foo/src/build/file.cs when it refers to the same file, so the breakpoint remains visible while debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100