microsoft / microsoft/vscode-cpptools

Breakpoint from setupCommands determinated as exception

Abierto
#14,565 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@sean-mcmanus ya está trabajando en esto.

Desde el 6/7/2026.

debugger more info needed
Lenguaje dominante
TypeScript
Estrellas
6.2k
Forks
1.7k
Merge medio
14 h 46 min
PR fusionados (30 d)
61

Descripción

Environment
  • OS and version: Ubuntu 20
  • VS Code: 1.127.0
  • C/C++ extension: 1.32.2
Bug Summary and Steps to Reproduce

I use testing extension which generates debugger config from template. I add break-insert via setupCommands:

				"setupCommands": [
					{
						"text": "-break-insert -t -f ${parentLabel[-2]}_${label}_Test::TestBody",
						"description": "Sets a breakpoint on test case body",
						"ignoreFailures": false
					}
				],

when breakpoint is hit is looks a bit frighteningly.
A red box with "an exception occurred" text.
Image

I expected that external breakpoint should behave same as planned breakpoint by VSCode by them self.

Debugger Configurations
{
  "name": "CreateLsp (BgpluIngressLsp▸dcsldf-blu-utests)",
  "request": "launch",
  "type": "cppdbg",
  "program": "/home/user/projects/output/linux-sim/debug/dcsldf-blu-utests",
  "args": [
    "--gtest_color=no",
    "--gtest_filter=BgpluIngressLsp.CreateLsp",
    "--gtest_also_run_disabled_tests",
    "--gtest_break_on_failure"
  ],
  "stopAtEntry": false,
  "cwd": "/home/user/projects/output/linux-sim/debug/",
  "environment": [],
  "externalConsole": false,
  "pipeTransport": {
    "debuggerPath": "/usr/bin/gdb",
    "pipeProgram": "/home/eak/hdd/FW.3//../../../../..//builder/builder.sh",
    "pipeArgs": [
      "run",
      "-pipe",
      "-work-dir",
      "/home/user/projects"
    ],
    "quoteArgs": false
  },
  "sourceFileMap": {
    "/home/user/projects": "/home/eak/hdd/FW.3/"
  },
    "setupCommands": [
    {
      "text": "-enable-pretty-printing",
      "ignoreFailures": true
    },
    {
      "text": "-break-insert -t -f BgpluIngressLsp_CreateLsp_Test::TestBody",
      "description": "Sets a breakpoint on test case body",
      "ignoreFailures": false
    }
  ],
  "logging": {
    "engineLogging": true,
    "trace": true,
    "traceResponse": true
  },
  "MIMode": "gdb",
  "__configurationTarget": 6
}
Debugger Logs
--> E (stopped): {"type":"event","event":"stopped","body":{"reason":"exception","threadId":167,"text":"Hit breakpoint 1 at 0x555555632622.","allThreadsStopped":true,"source":{"name":"ingress_lsp_tests.cpp","path":"/home/eak/hdd/FW.3/tests/bgplu-utests/ingress_lsp_tests.cpp","sources":[],"checksums":[]},"line":209,"column":1},"seq":426}
Other Extensions

No response

Additional Information

No response

Guía de contribución

Abrir la 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.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.