public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: archer@sourceware.org, utrace-devel@redhat.com
Subject: Re: gdbstub initial code, v11
Date: Wed, 22 Sep 2010 19:09:00 -0000	[thread overview]
Message-ID: <m34odh8ujr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100922022226.GA27400@redhat.com> (Oleg Nesterov's message of "Wed, 22 Sep 2010 04:22:26 +0200")

Oleg> But what about features? What should I do next? all-stop,
Oleg> thread-specific breakpoints (currently I have no idea what
Oleg> this means), or what?

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.

There was previously some discussion about some watchpoint-related
thing, I forget the details of that.

I don't think thread-specific breakpoints are exposed outside of gdb
yet.  If that is true, then implementing that would mean adding remote
protocol features and also other stuff inside gdb.  So, I would suggest
not tackling this yet.

Tom

  reply	other threads:[~2010-09-22 19:09 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 [this message]
2010-09-22 19:18   ` Jan Kratochvil
2010-09-23 22:12   ` Roland McGrath
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=m34odh8ujr.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=oleg@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).