Debugger not hitting breakpoints in 1.1.0-insiders3

After the recent update to cpptools v1.1.0-insiders3, I am no longer able to hit breakpoints. I can still "pause" the debugger and then step/print expressions etc. It is just breakpoints that no longer work. If I revert to cpptools v1.0.1, then breakpoints work again. I also recall that they worked with insiders2.

I'm on Debian 10.

VSCode Version: 1.50.1
C++ Extension Version: 1.1.0-insiders3

Here is my launch.json

        {
            "name": "Launch src/cgir_support dom_core_analysis_livenessAnalysis_pkgtest",
            "type": "cppdbg",
            "MIMode": "gdb",
            "miDebuggerPath": "sbgdb",
            "request": "launch",
            "program": "/local-ssd/ryanholt/test/matlab/derived/glnxa64/testbin/src/cgir_support/dom_core_analysis_livenessAnalysis_pkgtest",
            "cwd": "/local-ssd/ryanholt/test/matlab/src/cgir_support",
            "args": [
                "--gtest_filter=${input:testName}"
            ],
            "logging": {
                "moduleLoad": false,
                "engineLogging": true
            },
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                },
                {
                    "description": "Add file path directory",
                    "text": "directory /local-ssd/ryanholt/test",
                    "ignoreFailures": true
                }
            ],
            "sourceFileMap": {
                "/local-ssd/ryanholt/Bcgir_task_build.latest_pass": "/local-ssd/ryanholt/test",
                "/local-ssd/ryanholt/.Bcgir_task_build.latest_pass.sbsyncmaster": "/local-ssd/ryanholt/test",
                "/local-ssd/ryanholt/.Bcgir_task_build.latest_pass.sbsyncmaster.inprogress": "/local-ssd/ryanholt/test"
            },
            "presentation": {
                "group": "src/cgir_support_tasks",
                "hidden": false
            }
        },

Here is the output from enabling "engineLogging":

engineLogging.txt

Start by reproducing the breakpoint failure with cpptools v1.1.0-insiders3 on Debian 10 using the supplied launch.json, then compare it with cpptools v1.0.1 or insiders2. Inspect engineLogging.txt alongside the debugger configuration and verify that breakpoints are hit while pause, stepping, and expression printing continue to work.