microsoft / microsoft/vscode-cpptools

debugger cannot be used until extension is otherwise activated

Open
#10,684 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Environment
  • OS and Version: ubuntu 20.04
  • VS Code Version: 174.2
  • C/C++ Extension Version: v1.14.4
  • If using SSH remote, specify OS of remote machine:
    ubuntu 20.04
Bug Summary and Steps to Reproduce

Cannot debug my C++ application inside docker. Extension seems to be not activated.

Bug Summary:

  1. I start a docker container via cmd line. Then I attach to it via vs code. Which works without problems.
  2. Then I want to debug a C++ application which is running on this container.
  3. Then I installed the vs extension, because it is telling me that it is not installed.
  4. After checking the runtime status I see: "Not yet activated."

Expected behavior:
I can debug the application without any problems inside docker

Configuration and Logs
cannot find any logs, except in "Remote Server"


2023-03-15 15:31:46.244 [info] Extension installed successfully: ms-vscode.cpptools


### Other Extensions

_No response_

### Additional context

_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

No source file or test is named. Start by reproducing the activation state in a VS Code session attached to the Docker container and inspect the available Remote Server logs; done means the C++ debugger activates and can debug the application without requiring another activation step.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, docker, vscode
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.