title: ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". Unable to find Mach task port for process-id 1401
body: <p>I am trying to use GDB to run the debugger in VSCode in a C++ project, but I keep getting this error when running my debugger. I have set up a cert and everything and it is still giving me this error (I am running macOS Catalina version 10.15.4).</p>
  
  <p>Here is my launch.json file</p>
  
  <pre><code>{
     // 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": "(gdb) Launch",
              "type": "cppdbg",
              "request": "launch",
              "program": "${workspaceFolder}/build/Assignment8",
              "args": [],
              "stopAtEntry": false,
              "cwd": "${workspaceFolder}",
              "environment": [],
              "externalConsole": false,
              "MIMode": "gdb",
              "setupCommands": [
                  {
                      "description": "Enable pretty-printing for gdb",
                      "text": "-enable-pretty-printing",
                      "ignoreFailures": true
                  }
              ]
          }
      ]
  }
  </code></pre>
  
  <p>Here is my tasks.json file</p>
  
  <pre><code>{
      // See https://go.microsoft.com/fwlink/?LinkId=733558
      // for the documentation about the tasks.json format
      "version": "2.0.0",
      "tasks": [
          {
              "label": "echo",
              "type": "shell",
              "command": "make",
              "options": {
                  "cwd": "${workspaceFolder}/build"
              },
          }
      ]
  }
  </code></pre>
  
  <p>Additionally, I saw something about making a .gdbinit file, which I did in my root directory, and I placed the following command in it:</p>
  
  <pre><code>set startup-with-shell off
  </code></pre>
  
  <p>Any help with this issue would be greatly appreciated. </p>