Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "'gdb@sourceware.org'" <gdb@sourceware.org>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: GDB / GDBserver feature parity
Date: Fri, 10 Feb 2012 14:50:00 -0000	[thread overview]
Message-ID: <4F352EA5.9090304@redhat.com> (raw)
In-Reply-To: <4F352E27.40603@redhat.com>

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).
> 


      reply	other threads:[~2012-02-10 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 14:48 Pedro Alves
2012-02-10 14:50 ` Pedro Alves [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F352EA5.9090304@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox