Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Breakpoint from setupCommands determinated as exception

Open
#14,565 3 comments 0 reactions 1 assignee View on GitHub

@sean-mcmanus is already working on this.

Since Jul 6, 2026.

Assessment

This issue has not been assessed yet.

Description

debugger more info needed
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

Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
1d 4h
Merged PRs (30d)
60

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.

More from microsoft/vscode-cpptools

All issues in microsoft/vscode-cpptools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.