I've run into this exact issue before—VSCode doesn't realize your gdbserver task is ready to go, so it waits the full 10s timeout before letting you debug. The fix lies in telling VSCode exactly when your pre-launch task is done initializing with a properly configured problemMatcher.

Step-by-Step Fix #

Update your tasks.json to include a problemMatcher that watches for gdbserver's ready signal. Here's the corrected configuration:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label":"docker gdb",
      "command": "docker exec {containerName} /bin/bash -c \"pkill gdbserver; gdbserver localhost:9091 ./tests/ConfigurationTest.cpp_TestRunner\"",
      "isBackground": true,
      "type": "shell",
      "problemMatcher": [
        {
          "pattern": {
            "regexp": "^Listening on port.*$",
            "file": 0,
            "location": 0,
            "message": 0
          },
          "background": {
            "activeOnStart": true,
            "beginsPattern": "^Process.*created; pid =.*$",
            "endsPattern": "^Listening on port.*$"
          },
          "owner": "cpp",
          "severity": "info"
        }
      ]
    }
  ]
}

Why This Works #

• isBackground: true: Tells VSCode this task runs indefinitely (since gdbserver stays alive during debugging).
• background.beginsPattern: Matches the first line of output from gdbserver (Process ... created; pid = ...) to mark the task as started.
• background.endsPattern: Matches the critical "Listening on port 9091" line—this is the signal VSCode needs to know the task is ready, so it stops waiting and launches the debugger immediately.
• The pattern block ensures VSCode recognizes this output as a valid task completion signal (even though it's just info, not an error/warning).

What Was Wrong Before #

Your earlier attempt with activeOnStart: true was missing the beginsPattern and endsPattern definitions. Without these, VSCode had no way to detect when gdbserver finished initializing, so it waited the full 10s timeout before giving up and showing the error.

Verify the Fix #

After updating tasks.json:

1. Start your debug session as usual.
2. You'll see the gdbserver output in the terminal.
3. As soon as "Listening on port 9091" appears, VSCode will immediately connect to the debugger—no more 10s wait, no more error prompt.

Just make sure to replace {containerName} with your actual Docker container name, and double-check that the port in gdbserver matches what's in your launch.json (9091 in your case).

内容的提问来源于stack exchange，提问作者geekydel