Breakpoint from setupCommands determinated as exception

[zhekaso]

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.

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

[sean-mcmanus]

@zhekaso Sorry, I'm not understanding what the issue is. Can you give more info on what you expect the behavior to be?

[zhekaso]

When setting a breakpoint manually via setupCommands using -break-insert, the execution stops as expected, but the UI incorrectly displays a disruptive red "Exception" error box.

If I set a breakpoint directly in the IDE gutter, it stops normally without any error box.

I checked the logs and confirmed that the debugger backend originally sends the correct reason: "reason": "breakpoint-hit". However, at some stage, this event is mistakenly converted to "reason": "exception", which triggers the messy error UI. This scenario with setupCommands should not lead to an exception box.