The remote debugging connection cannot be disconnected normally

[dingzhou-beck]

ENV

host:

os:  windows10

gdb: 10.2

cdt-gdb-vscode： v2.0.5

target:

arch: arm32

gdbserver: 7.6

I am currently using cdt-gdb-vscode for remote debugging in VS Code. Here is my configuration file:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "arm32_debug",
            "type": "gdbtarget",
            "request": "launch",
            "gdbNonStop": true,
            "gdb": "d:\\debugger_gdb\\aarch64-linux-gnu-gdb.exe",
            "program": "${workspaceFolder}\\build\\app.elf",
            "logFile": "${workspaceFolder}\\.vscode\\debug.log",
            "verbose": true,
            "cwd": "${workspaceFolder}",
            "target": {
                "type": "remote",
                "host": "10.0.2.20",
                "port": "64025",
                "serverParameters": []
            }
        }
    ]
}

Problem：

1.The program executed normally and completed, but an error message appeared: You can't do that when your target is 'exec'; however, gdbserver exited normally.

2. When the debugging session is started and stops at a certain breakpoint, if 'stop' is directly used, the remote gdbserver does not terminate.

logs:

gdbserver stoppedTo client: {"seq":0,"type":"response","request_seq":12,"command":"disconnect","success":true}

This seems to merely disconnect the connection, but it does not terminate the remote gdbserver process.

It is worth noting that I also used cpp-dbg in VSCode to remotely debug with the same environment and program, and it worked well. Moreover, when executing "stop", it first sends a "kill" command to gdbserver and then exits gdb. Is this a difference in the debugging adapter?

Do you know if there are any other restrictions? Or is there a problem with my debugging configuration? Thank you for your correction.

[jonahgraham]

There may be a mismatch be in expectations. The adapter does not have a way of automatically launching gdbserver on a remote machine. Is 10.0.2.20 the IP address of your ARM machine?

Perhaps what this needs to be is converted to a feature request that adds launching gdbserver on remote boards?

In the meantime, you can manually launch gdbserver on the remote (e.g. ssh 10.0.2.20 gdbserver :1234) and then something like this may work.

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "arm32_debug",
            "type": "gdbtarget",
            "request": "attach",
            "gdbNonStop": true,
            "gdb": "d:\\debugger_gdb\\aarch64-linux-gnu-gdb.exe",
            "program": "${workspaceFolder}\\build\\app.elf",
            "logFile": "${workspaceFolder}\\.vscode\\debug.log",
            "verbose": true,
            "cwd": "${workspaceFolder}",
            "target": {
                "type": "remote",
                "host": "10.0.2.20",
                "port": "1234",
                "serverParameters": [":1234"]
            }
        }
    ]
}