Failing to start debugger on macOS

Type: Debugger

Describe the bug

• OS and Version: macOS 10.15.5 (19F101)
• VS Code Version: 1.46.1
• C/C++ Extension Version: v0.28.3
• Other extensions you installed (and if the issue persists after disabling them): I have other extensions, but the issue persists if i disable them all except for the cpptools extension
• Trying to start the debugger, however nothing happens like a progress indication for a second. This used to work 3-6 months ago.

Additional context
My launch.json contents:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(lldb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/tool",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "lldb",
            "miDebuggerPath": "/usr/bin/lldb",
            "logging": {
                "trace": true,
                "traceResponse": true,
                "engineLogging": true
            }
        }
    ]
}

Output of code --log trace --verbose when hitting the debug button:

[main 2020-06-25T08:00:41.340Z] menubarService#updateMenubar 1
[11243:0625/100042.272838:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent:  onDebug", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[11243:0625/100042.401881:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent:  onDebugResolve", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[11243:0625/100042.402678:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent:  onDebug", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[11243:0625/100042.423564:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent:  onDebug", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[11243:0625/100042.477098:INFO:CONSOLE(1670)] "%cTRACE color: #888 [File Watcher (node.js)] [ADDED] /Users/tobias/Library/Application Support/Code/logs/20200625T100002/ms-vscode.cpptools.txt", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[main 2020-06-25T08:00:42.573Z] menubarService#updateMenubar 1
[11243:0625/100042.702000:INFO:CONSOLE(1670)] "%cTRACE color: #888 [File Watcher (node.js)] >> normalized [ADDED] /Users/tobias/Library/Application Support/Code/logs/20200625T100002/ms-vscode.cpptools.txt", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[11243:0625/100043.924122:INFO:CONSOLE(1670)] "%c  ERR color: #f33 timeout after 1000 ms: Error: timeout after 1000 ms
    at t.RawDebugSession.handleErrorResponse (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3160:190)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3159:451
    at async t.RawDebugSession.shutdown (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3157:536)", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[main 2020-06-25T08:00:44.686Z] menubarService#updateMenubar 1

Beginne mit der launch.json-Konfiguration und reproduziere den Fehler mit dem gemeldeten Befehl code --log trace --verbose. Untersuche das erzeugte ms-vscode.cpptools.txt-Protokoll zusammen mit der Timeout-Ausgabe, um festzustellen, an welcher Stelle der Start des Debuggers stoppt. Als erledigt gilt die Aufgabe, wenn die gemeldete macOS-Konfiguration den Debugger startet und einen sichtbaren Startfortschritt liefert.