Running GDB on the deployment machine (lose the gdbserver)

[amirs]

When using a computer for building, and another for deployment
currently VisualGDB runs a `gdbserver` on the deployment, and attaches via the network with `gdb` running on the building machine.

If I have a working gdb for the deployment machine, is it possible to the lose this indirection (aka debugging without gdbserver),
and run (via ssh, ofcourse) the `gdb` on the deployment machine directly?

This mean the building machine will only be used for compiling, and is not involved in the debugging process.

This kind of solution will solve a previous post of mine, where I wanted gdbserver to listen on dynamic port, to avoid conflict where many users are using the deployment machine (http://forum.sysprogs.com/viewtopic.php?f=5&t=2839),
but does this kind of solution adds any “stability” to the debugging? I don’t know..

What do you think?

[support]

Hi,

Using remote gdb for a binary built with a cross-compiled would not be straight-forward, so we would recommend using dynamic gdbserver port instead.
Please see the reply in viewtopic.php?f=5&t=2839

[Author]

Posts