How to set up code path when debug C++ in Visual Studio - c++

Question

I am following this official Visual Studio site to start developing C++ in Visual Studio: https://code.visualstudio.com/docs/languages/cpp#:~:text=C%2FC%2B%2B%20support%20for%20Visual%20Studio%20Code%20is%20provided,use%20the%20keyboard%20shortcut%20%28Ctrl%2BShift%2BX%29.%20Search%20for%20%27C%2B%2B%27. I have MinGW installed as suggested.
I can build the code and it runs correctly.
When I set a break point and run debug, the break point is ignored. The following messages appears several times in the Debug Console:
PS C:\Users\Cheng\Documents\Temp\HelloWorld> & 'c:\Users\Cheng\.vscode\extensions\ms-vscode.cpptools-1.13.9-win32-x64\debugAdapters\bin\WindowsDebugLauncher.exe' '--stdin=Microsoft-MIEngine-In-ccgsybc5.exz' '--stdout=Microsoft-MIEngine-Out-bwaebfti.urx' '--stderr=Microsoft-MIEngine-Error-rwnjcwal.lr2' '--pid=Microsoft-MIEngine-Pid-mj2o2p2s.eil' '--dbgExe=/msys64/usr/bin/gdb.exe' '--interpreter=mi'
When I set "stopAtEntry" to true in lauch.json, I see the following log in the Debug Console indicating the correct code path:
Thread 1 "HelloWorld" hit Breakpoint 1, main () at C:\Users\Cheng\Documents\Temp\HelloWorld\HelloWorld.cpp:5
But a new file pop up, with empty content and the following path:
C:\Users\Cheng\Documents\Temp\HelloWorld\C\Users\Cheng\Documents\Temp\HelloWorld\HelloWorld.cpp
The content of the launch.json is the following:
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/${fileBasenameNoExtension}.exe",
"args": [],
"stopAtEntry": false,
"cwd": "${fileDirname}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "/msys64/usr/bin/gdb.exe",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
},
{
"description": "Set Disassembly Flavor to Intel",
"text": "-gdb-set disassembly-flavor intel",
"ignoreFailures": true
}
]
},
]
}
I think that it is just an issue of specifying the correct debug path.
Can anyone help me on this configuration issue? Very much appreciated your help.
CP