public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	utrace-devel@redhat.com, archer@sourceware.org
Subject: Re: gdbstub initial code, v11
Date: Thu, 23 Sep 2010 22:12:00 -0000	[thread overview]
Message-ID: <20100923212423.B4EF540048@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of  Wednesday, 22 September 2010 13:09:12 -0600 <m34odh8ujr.fsf@fleche.redhat.com>

> I think it would be good to implement a feature that shows how this
> approach is an improvement over the current state of gdb+ptrace or
> gdb+gdbserver.
> 
> Exactly what feature this should be... I don't know :-)
> I would imagine something performance-related.

My vague notion was that we'd get it working well enough to have basic
parity with native or gdbserver on some realish test cases, and then just
look at the protocol interaction log to see cases where we could reduce
round-trips between gdb and the stub.  Some of those are bound to entail
protocol extensions and gdb changes to exploit them.  Off hand, the Z cases
might be the only things that won't need that.


Thanks,
Roland

  parent reply	other threads:[~2010-09-23 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  2:26 Oleg Nesterov
2010-09-22 19:09 ` Tom Tromey
2010-09-22 19:18   ` Jan Kratochvil
2010-09-23 22:12   ` Roland McGrath [this message]
2010-09-22 22:06 ` Frank Ch. Eigler
2010-09-22 23:18   ` Oleg Nesterov
2010-09-22 23:39     ` Frank Ch. Eigler
2010-09-22 23:48       ` Oleg Nesterov
2010-09-23 22:03         ` Roland McGrath
2010-09-23 22:12           ` Frank Ch. Eigler

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=20100923212423.B4EF540048@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=oleg@redhat.com \
    --cc=tromey@redhat.com \
    --cc=utrace-devel@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).