Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Debug launch with multiproject solution

Abierto
  • ¿Algo no está bien?
#3 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
vscode
Área
devtools, embedded-iot

Línea de trabajo

Start with the launch.json and task.json configurations shown in the issue, then trace how the solution and application file are selected for a multiproject CMSIS solution. Compare the single-project and three-project cases; done means the launch and flash tasks select the application project rather than the first library project without a hard-coded output path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Windows 10
Arm debugger 1.0.0 VSC extension

When I generate a solution with a single project all works fine.
my launch.json looks like:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Arm Debug",
"type": "arm-debug",
"request": "launch",
"serialNumber": "${command:device-manager.getSerialNumber}",
"program": "${command:embedded-debug.getApplicationFile}",
"cmsisPack": "${command:cmsis-csolution.getTargetPack}",
"connectMode": "auto",
"debugFrom": "main",
"probe": "CMSIS-DAP",
"programMode": "auto",
"resetMode": "auto",
"preLaunchTask": "Flash Device"
}
]
}
and my task json looks like:
{
"version": "2.0.0",
"tasks": [
{
"label": "Build Context",
"type": "cmsis-csolution.build",
"solution": "${command:cmsis-csolution.getSolutionPath}",
"rebuild": false,
"problemMatcher": [],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "Flash Device",
"type": "arm-debugger.flash",
"serialNumber": "${command:device-manager.getSerialNumber}",
"program": "${command:arm-debugger.getApplicationFile}",
"cmsisPack": "${command:device-manager.getDevicePack}",
"problemMatcher": [],
"dependsOn": "Build Context"
}
]
}

This works just fine for singe project solution. I can build flash and debug.
If I have a solution that contains three projects, the first two listed are library build projects and the third is the actual app with dependency of the previous two libraries. This also builds fine but debug launch seems to try to flash and debug only the first listed project (the library).
I know I could hard code the absolute build output path in the launch.json's "program" node but that does not seem like the right thing to do.
Is there another way?

Lenguaje dominante
Sin datos de lenguaje
Estrellas
7
Forks
3
Sin PR fusionados en 30 d

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ARM-software/vscode-arm-debugger

Todos los issues de ARM-software/vscode-arm-debugger

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.