microsoft / microsoft/vscode-cpptools
C Source 'Go To Definition' error in Remote-SSH mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Issue Type: Bug
when i open a C Source Project in linux server, and this project has a Symbol Link path.
- first, i open this project in VSC Remote-SSH mode, and it recognized as a symbolic link path“/workteam/xxxxxx/data/work/V1.27.0/src/net/rest/netdisk_bd_v2”
- open a C file, and select a function, use to 'Go to Definition' jump to a function, and this function is in the same file. but it open another window to show this function.
The original path is the symbolic link path, After 'Go to Definition' is to open the path to a real path.
(I'm not sure if this question is related to symbolic links, it's just my scene)
Extension version: 0.26.2
VS Code version: Code - Insiders 1.41.0-insider (97855786a014be2440751b038b373c3726e11fe8, 2019-12-03T05:40:39.806Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 3.13.0-128-generic
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz (4 x 3408) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 7.89GB (2.44GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 67% |
| Item | Value |
|---|---|
| Remote | SSH: CPL |
| OS | Linux x64 3.13.0-128-generic |
| CPUs | Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (12 x 2599) |
| Memory (System) | 23.55GB (0.83GB free) |
| VM | 100% |
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
Reproduce the C Source “Go to Definition” flow in VS Code Remote-SSH with the symbolic-link project path described in the issue. Start at the Go to Definition entry point and compare the opened symbolic-link path with the resolved real path. Done means navigation keeps the expected project path instead of opening a separate window at the real path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100