microsoft / microsoft/vscode-cpptools
Can't find a C++ source file on ecryptfs home directory during debug process on Ubuntu.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
From @Schmerzmittel on April 6, 2017 22:24
- VSCode Version: 1.11.1
- OS Version: Ubuntu 16.10 4.10.8 Generic Kernel.
Every time I tried to debug a C++ software with breakpoints, Code said it could not find the source code file and created a empty file at a strange place (/home/"myusername"/353254270354204234/"projectnameakamyprecious"/main.cpp). The debugging process worked; however, this issue made debugging process little tricky since I was not able to follow up with the debugger.
Code can open files without any problems, but whenever I use the debugger, Code opens a new file and sets step on the empty file.
I am referring to ecryptfs because that's what I am using, and I am thinking that the software [ecryptfs] is causing the problem.
Steps to Reproduce:
- Install Ubuntu with ecryptfs (Home directory encryption).
- Debug a C++ file with a breakpoint.
- Notice that Code does not open the source file with breakpoints but a new one.
Copied from original issue: Microsoft/vscode#24148
Contributor guide
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
Start by reproducing the breakpoint behavior in the VSCode C++ debugger on an Ubuntu home directory encrypted with ecryptfs, following the listed steps. Trace how the debugger maps the reported source path to the workspace file; done means breakpoints open and step through the actual C++ source instead of an empty generated file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, ubuntu, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100