VSCode GDB Launch Settings for GStreamer's "gcheck" test framework

launch.json

{
    "configurations": [
        {
            "name": "Debug GCheck Test",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/path/to/executable",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                },
                {
                    "description": "Enable randomization for gdb",
                    "text": "-enable-randomization",
                    "ignoreFailures": true
                },
                {
                    "description": "GDB stays attached to both processes on fork for gdb",
                    "text": "-gdb-set detach-on-fork off",
                    "ignoreFailures": true
                },
                {
                    "description": "Follow child on fork for gdb",
                    "text": "-gdb-set follow-fork-mode child",
                    "ignoreFailures": true
                }
            ]
        }
    ]
}

The first two setupCommands are typical things. The second two though are necessary to keep the gdb instance attached to the unit under test. Additionally, stopAtEntry: true is often required for a breakpoint within a test to actually be registered across the reattachment behavior. If you find that running false there works for you, then perhaps they fixed this.