debugger doesn't hit breakpoint in my c++ code when assign a map by array

Type: Debugger

debugger doesn't hit breakpoint when assign a map with array.
However it can hit breakpoint normally when assign a map with insert method.

Describe the bug

• OS and Version: WIN10
• VS Code Version: v1.42.0
• C/C++ Extension Version: 0.26.3
• Other extensions you installed (and if the issue persists after disabling them):
• A clear and concise description of what the bug is.

To Reproduce
Please include a code sample and launch.json configuration.

launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}/${fileBasenameNoExtension}.exe",
"args": [],
"stopAtEntry": true,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": true,
"internalConsoleOptions": "neverOpen",
"MIMode": "gdb",
"miDebuggerPath": "C:\LLVM\bin\gdb.exe",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": false
}
],
"preLaunchTask": "Compile"
}
]
}

Steps to reproduce the behavior:
Debugger doesn't hit breakpoint when assign a map with array. ( as attached screen capture code)
However it can hit breakpoint normally when assign a map with insert method.

Additional context
If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json
Add any other context about the problem here including log or error messages in your Debug Console or Output windows.

Start by reproducing the breakpoint behavior described in the issue with the provided launch.json on Windows 10, comparing map assignment from an array with map.insert. The issue does not name a source file or test, so first obtain the missing code sample and debugger logs. Done means the differing breakpoint behavior is isolated and the debugger behavior is corrected or clearly documented with regression coverage.