From: Kevin Buettner <kevinb@redhat.com>
To: archer@sourceware.org
Subject: Re: gdbstub initial code, v15
Date: Mon, 01 Nov 2010 18:23:00 -0000 [thread overview]
Message-ID: <20101101112348.43afe201@mesquite.lan> (raw)
In-Reply-To: <20101101175927.GA17098@redhat.com>
On Mon, 1 Nov 2010 18:59:27 +0100
Oleg Nesterov <oleg@redhat.com> wrote:
> Next: hardware watchpoints. But this is tricky, and right now I am
> not sure ugdb can do this (at least unless we ignore conflicts with
> other users of debugregX/ptrace_bps).
For the time being, I would just ignore those conflicts. Later on,
perhaps, it might make sense to implement facilities by which the
various users can lock the resources in question.
Kevin
prev parent reply other threads:[~2010-11-01 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 18:06 Oleg Nesterov
2010-11-01 18:23 ` Kevin Buettner [this message]
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=20101101112348.43afe201@mesquite.lan \
--to=kevinb@redhat.com \
--cc=archer@sourceware.org \
/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).