Talk:Gdbserver

I think it would be nice to have a section with History and Features. --jbc (talk) 13:02, 13 February 2010 (UTC)[reply]

WP:NOHOWTO

Would it be wise to add dates in this article, especially the date of creation of the gdbserver project? (I guess 2005, I don't know) 77.159.196.124 (talk) 08:55, 6 February 2024 (UTC)[reply]

The source code is only needed on the host. (This is already mentioned in the article.)
Debugging symbols are only needed on the host. The binary for the target can be stripped, so it can be transferred to the target more quickly and needs less space there.
gdbserver is much smaller than gdb itself, thus consuming fewer resources on the target for its own purposes.
gdbserver only provides low-level functionality, so it can be ported to other – possibly exotic or limited – hardware platforms more easily than the full-blown gdb.
gdb can directly interact with higher-level front-end tools (such as IDEs) that run on the host, so these tools do not even need to be aware of the remote connection.
A customized variant of gdbserver can also run on the host itself, but still hide the low-level access to the target (e. g. via JTAG) from gdb.
gdbserver can also run as a background service on the target, so that logging in to a shell on the target is not necessarily required.