From: Yao Qi <yao@codesourcery.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: [RFC] gelf - user space probe debugger
Date: Mon, 24 Jan 2011 22:35:00 -0000 [thread overview]
Message-ID: <4D3DFEBC.8030508@codesourcery.com> (raw)
In-Reply-To: <20110124161020.GC3694@jolsa.brq.redhat.com>
On 01/25/2011 12:10 AM, Jiri Olsa wrote:
> hi,
>
> I started a debugger project. It's based on the user space backport
> of optimized kprobes (djprobes) and RSP stub implementation.
>
First of all, it is a nice piece of work!
> The debugger is implemented as a preloaded shared library,
> which handles all the debugger work, hence no kernel ptrace
> is needed.
Here are some questions, and I am sorry if my questions go out of scope
here.
1. Do you plan to handle signal without ptrace support? In
ptrace-debugger, we can know every signal delivered to debuggee process.
How can we do that in your probe-debugger?
2. Do you plan to support hardware single-step on x86?
>
> I'd like to ask for opinions if there'd be users for such thing,
> and if it's worth to continue on this..
AFAIK, it is not easy to replace ptrace-based debugger by probe-based
debugger completely. However, probe-based technology can be a
complementary part to existing ptrace-based debugger, especially to
efficient implementation of breakpoint/watchpoint/tracepoint in some
cases. Shortly, it is good to put both ptrace-based and probe-based
into single debugger, and maximize their advantages, and minimize their
disadvantages.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-01-24 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 16:10 Jiri Olsa
2011-01-24 22:35 ` Yao Qi [this message]
2011-01-25 9:35 ` Jiri Olsa
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=4D3DFEBC.8030508@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jolsa@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