From: "Frank Ch. Eigler" <fche@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 23:39:00 -0000 [thread overview]
Message-ID: <20100922233909.GF2727@redhat.com> (raw)
In-Reply-To: <20100922231451.GA11198@redhat.com>
Hi -
On Thu, Sep 23, 2010 at 01:14:51AM +0200, Oleg Nesterov wrote:
> > (It seems to me that a pure gdb report, without a synthetic
> > self-injected SIGTRAP, should be fine.)
>
> What do you mean?
(Never mind, I'm probably just confused about what you were asking.)
> > > Next: fully implement g/G/p/P, currently I am a bit confused...
> > > But what about features? [...]
> >
> > You could dig out the old "fishing plan". One demonstrated
> > improvement was from simulating (software) watchpoints within the
> > gdb stub, instead of having gdb fall back to issing countless
> > single-steps with memory-fetch inquiries in between.
>
> When I do 'watch', gdb sends '$Z2'. I am a bit confused, iirc it
> was decided I shouldn't play with Z packets now. But I won't
> argue.
There are Z packets and then there are Z packets. The ones Roland
told you not to worry about are Z0/Z1 related to (code) breakpoints,
which should be implemented via uprobes at some point.
The ones I'm talking about are Z2/Z3 for (data) watchpoints.
- FChE
next prev parent reply other threads:[~2010-09-22 23:39 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
2010-09-22 22:06 ` Frank Ch. Eigler
2010-09-22 23:18 ` Oleg Nesterov
2010-09-22 23:39 ` Frank Ch. Eigler [this message]
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=20100922233909.GF2727@redhat.com \
--to=fche@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).