Talk:Gdbserver
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
I think it would be nice to have a section with History and Features. --jbc (talk) 13:02, 13 February 2010 (UTC)
This article sounds a lot like a how-to.Jasper Deng (talk) 05:16, 13 March 2011 (UTC)
Year of creation[edit]
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)
Why is it useful?[edit]
- The source code is only needed on the host.[1] (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.[2]
gdbserveris much smaller thangdbitself, thus consuming fewer resources on the target for its own purposes.[3]gdbserveronly provides low-level functionality, so it can be ported to other – possibly exotic or limited – hardware platforms more easily than the full-blowngdb.[4]gdbcan 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.[5]- A customized variant of
gdbservercan also run on the host itself, but still hide the low-level access to the target (e. g. via JTAG) fromgdb.[6] gdbservercan also run as a background service on the target, so that logging in to a shell on the target is not necessarily required.[7]
References[edit]
- ^ "Running gdbserver". Debugging with GDB: the GNU Source-Level Debugger. Free Software Foundation, Inc. Retrieved 2024-06-23.
You need a copy of the program you want to debug, including any libraries it requires.
- ^ "Running gdbserver". Debugging with GDB: the GNU Source-Level Debugger. Free Software Foundation, Inc. Retrieved 2024-06-23.
gdbserver does not need your program's symbol table, so you can strip the program if necessary to save space.
- ^ "Using the gdbserver Program". Debugging with GDB: the GNU Source-Level Debugger. Free Software Foundation, Inc. Retrieved 2024-06-23.
gdbserver is sometimes useful […] because it is a much smaller program than GDB itself.
- ^ "Using the gdbserver Program". Debugging with GDB: the GNU Source-Level Debugger. Free Software Foundation, Inc. Retrieved 2024-06-23.
gdbserver […] is also easier to port than all of GDB, so you may be able to get started more quickly on a new system by using gdbserver.
- ^ "Connecting to gdbserver". Debugging with GDB: the GNU Source-Level Debugger. Free Software Foundation, Inc. Retrieved 2024-06-23.
Run GDB on the host system.
- ^ "nios2-gdb-server". Nios II Software Developer Handbook. Intel. Retrieved 2024-06-23.
Translates GNU debugger (GDB) remote serial protocol packets […] to JTAG transactions with a target Nios II processor.
- ^ "TCP port allocation lifecycle of gdbserver". Debugging with GDB: the GNU Source-Level Debugger. Free Software Foundation, Inc. Retrieved 2024-06-23.
[F]or target extended-remote, gdbserver stays running even with no processes left. […] When gdbserver stays running, GDB can connect to it again later.
--89.246.164.187 (talk) 17:04, 21 June 2024 (UTC)