From: Roland McGrath <roland@redhat.com>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: Oleg Nesterov <oleg@redhat.com>,
utrace-devel@redhat.com, archer@sourceware.org,
Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: gdbstub initial code, v8
Date: Fri, 10 Sep 2010 10:02:00 -0000 [thread overview]
Message-ID: <20100910100151.8D7E7405D5@magilla.sf.frob.com> (raw)
In-Reply-To: Frank Ch. Eigler's message of Monday, 6 September 2010 22:59:37 -0400 <y0mr5h6xnqe.fsf@fche.csb>
> Please note that last year's gdbstub prototype used kernel uprobes as
> an optional gdb breakpoint implementation (i.e., a backend for the Z
> packets). When/if the lkml uprobes patches actually get merged, ugdb
> should also use them.
That's something for later, and it's not quite so simple. If a utrace
engine ever uses uprobes, it probably would need to use the utrace-based
version of uprobes. If something different goes in upstream, it remains
to be seen how it would interact with utrace, and there would be
specific work required for that. There are many more issues about that
too. At any rate, this is all a distraction at the moment, and Oleg
doesn't need any more of those!
Thanks,
Roland
next prev parent reply other threads:[~2010-09-10 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 22:44 Oleg Nesterov
2010-09-05 19:41 ` Jan Kratochvil
2010-09-06 18:21 ` Oleg Nesterov
2010-09-06 18:31 ` Jan Kratochvil
2010-09-06 20:48 ` Oleg Nesterov
2010-09-07 2:59 ` Frank Ch. Eigler
2010-09-08 19:24 ` Oleg Nesterov
2010-09-10 10:02 ` Roland McGrath [this message]
2010-09-06 18:27 ` gdbstub initial code, v8 && ptrace Oleg Nesterov
2010-09-06 19:45 ` Oleg Nesterov
2010-09-06 21:02 ` Oleg Nesterov
2010-09-10 10:10 ` Roland McGrath
2010-09-10 19:10 ` Oleg Nesterov
2010-10-13 7:14 ` Roland McGrath
2010-10-15 13:57 ` Oleg Nesterov
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=20100910100151.8D7E7405D5@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=archer@sourceware.org \
--cc=fche@redhat.com \
--cc=jan.kratochvil@redhat.com \
--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).