microsoft / microsoft/vscode-cpptools
cannot use chinese filename when debugging cpp files.
Open
Nobody has claimed this yet.
debugger
duplicate
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
From @alanx172 on November 15, 2017 2:56
- VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T21:22:49.932Z)
- OS Version: Windows_NT x64 10.0.16299
- Extensions:
| Extension | Author (truncated) | Version |
|---|---|---|
| html-snippets | abu | 0.1.0 |
| vscode-html-css | ecm | 0.1.8 |
| php-debug | fel | 1.11.1 |
| php-intellisense | fel | 1.5.4 |
| code-runner | for | 0.8.3 |
| cpptools | ms- | 0.14.2 |
| vscode-hexdump | sle | 1.6.0 |
| html-preview-vscode | tht | 0.1.1 |
Steps to Reproduce:
- edit a cpp file with chinese filename.
- compiling/building is ok.
- debugger cannot find the source file. but it's ok when using english filenames.
Reproduces without extensions: Yes/No
yes while disabling all extensions
Copied from original issue: Microsoft/vscode#38368
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 issue on Windows with a C++ file whose filename contains Chinese characters, using the debugger described in the report. Compare source-file lookup with an equivalent English filename and trace the debugger's source resolution path. Done means debugging opens the Chinese-named source file without changing the build setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100