This is the mail archive of the
mailing list for the GDB project.
Re: GDB / GDBserver feature parity
- From: Pedro Alves <palves at redhat dot com>
- To: "'gdb at sourceware dot org'" <gdb at sourceware dot org>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Fri, 10 Feb 2012 14:50:13 +0000
- Subject: Re: GDB / GDBserver feature parity
- References: <4F352E27.email@example.com>
- Reply-to: "'gdb at sourceware dot org'" <gdb at sourceware dot org>
Sorry, meant to send this to the gdb@ list...
On 02/10/2012 02:48 PM, Pedro Alves wrote:
> Just a short note that I've been, and will for a while be working on
> local/remote debugging feature parity.
> See <http://sourceware.org/gdb/wiki/LocalRemoteFeatureParity>.
> " GDBserver supports features native debugging does not support. Native debugging supports
> features GDBserver does not support.
> The aim of this project is bridging the gap between both worlds.
> Neither target backend is a superset of the other currently. A secondary goal of this project
> is making it possible to share a single target backend between native debugging and
> GDBserver (on GNU/Linux at first), by making the GDBserver backend support all of GDB's
> native backend's features (and more).
> I've identified features that either of the local and gdbserver backends support
> that the other doesn't. Please do feel free to add new points to the
> tables/lists in the wiki above, and, help with the coding, of course.
> Any kind of help is most welcome!
> This is a step towards support for parallel distributed debugging
> (programs that run on multiple machines controlled by a single gdb).