microsoft / microsoft/vscode-cpptools

Source Server support is missing

Open
#12,777 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger help wanted
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Environment
  • OS and version: Windows
  • VS Code: 1.93
  • C/C++ extension: 1.21.6
  • OS and version of remote machine (if applicable): N/A
  • GDB / LLDB version: N/A
Bug Summary and Steps to Reproduce

Bug Summary:
It is possible to put source-server information in the pdb files. (See https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/the-srcsrv-ini-file)
With this, you can add a link to a git/svn/... server and explain how to get the source code from it.
If you debug in visual studio, it extracts this information from the PDB and asks if you trust the command to download the sources. If you do, you will see the sources as they were stored in the git/svn/... server for that specific revision.

Steps to reproduce:

  1. Create a binary with pdbs and source server info
  2. Run the binary
  3. Make dump file from it (taskmanager)
  4. Open the dump file in VS Code
  5. See that the sources are not loaded.
Debugger Configurations
`
`
        {
            "name": "Open Dump File (Windows)",
            "type": "cppvsdbg",
            "request": "launch",
            "dumpPath": "C:/Temp/process.DMP",
            "program": "unused field in case of opening dumps, that is required in the json",
            "args": [],
            "cwd": "${workspaceFolder}",
            "environment": [],
            "requireExactSource": false,
            "symbolOptions": {
                "searchPaths": [
                    "file://servername/directory"
                ],
                "searchMicrosoftSymbolServer": true,
                "cachePath": "E:/Cache",
            },
            "console": "internalConsole",
            "logging": {
                "exceptions": true,
                "programOutput": true,
                "moduleLoad": true,
                "engineLogging": true,
                "trace": true,
                "traceResponse": true
            }
        },


### Debugger Logs

```shell
N/A
Other Extensions

No response

Additional Information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the cppvsdbg dump-file flow and investigate how PDB source information is currently handled. Use the provided Windows dump reproduction and source-server documentation as the first checks. Done means opening the dump can retrieve the revision-specific sources from the configured server, with an appropriate trust prompt.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.