microsoft / microsoft/vscode-cmake-tools

Enhancement: integration with another extension: cortex-debug

Open
#625 5 comments 8 reactions 0 assignees View on GitHub
embedded Feature: build
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

It would be great if this extention could we integrated with another.

Currently I have to take the following steps if I want to change code after debugging:
1) Switch to cmake-tools extension
2) Press build
3) Switch to cortex-debug extension
4) Press debug

By forgetting step 3, the project debugs without being built. This is unwanted.

I know it's possible to integrate the debugger actions into CMake but this is not what I am looking for, as I need the register view, stack trace, disassembly etc.

I made a mockup to clearify things:
![vscbuilddebug](https://user-images.githubusercontent.com/44534542/50708823-f6363600-1065-11e9-89c7-6caa417f6069.png)

Thanks!
Rolf

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the CMake Tools build action and the cortex-debug launch workflow described in the issue. Trace how VS Code switches between these extensions and identify the integration points needed to build before debugging. Done means a cortex-debug launch uses the current build without manual extension switching while retaining its register, stack trace, and disassembly views.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, typescript, vscode
Domain
build-system, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.