From: fche@redhat.com (Frank Ch. Eigler)
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
robertsong.japan@gmail.com, gdb@sourceware.org
Subject: Re: Why no hwatch command in gdb ?
Date: Thu, 10 Mar 2011 14:47:00 -0000 [thread overview]
Message-ID: <y0mwrk7vxqo.fsf@fche.csb> (raw)
In-Reply-To: <20110310115543.GA5414@host1.jankratochvil.net> (Jan Kratochvil's message of "Thu, 10 Mar 2011 12:55:43 +0100")
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> [...]
> But it being discussed for upstream kernel that the DR registers access via
> PTRACE_POKEUSER is broken anyway and GDB should use the existing hardware
> watchpoints support in Linux kernel perf via some higher level interface
> (still probably through the ptrace syscall).
While a new kernel interface wouldn't be able to fabricate any
hardware-watchpoint resources after they're exhausted, a properly
designed one should be able to evaluate software watchpoints much
faster.
- FChE
next prev parent reply other threads:[~2011-03-10 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 7:25 robert song
2011-03-10 8:12 ` Jan Kratochvil
2011-03-10 10:09 ` robert song
2011-03-10 10:34 ` Jan Kratochvil
2011-03-10 11:26 ` Eli Zaretskii
2011-03-10 11:34 ` Joel Brobecker
2011-03-10 12:27 ` Pedro Alves
2011-03-10 11:55 ` Jan Kratochvil
2011-03-10 14:47 ` Frank Ch. Eigler [this message]
2011-03-10 12:18 ` robert song
2011-03-10 13:45 ` Jan Kratochvil
2011-03-10 14:47 ` Philippe Waroquiers
2011-03-10 21:04 ` Tom Tromey
2011-03-11 7:58 ` Philippe Waroquiers
2011-03-11 17:48 ` Daniel Jacobowitz
2011-03-10 8:23 paawan oza
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=y0mwrk7vxqo.fsf@fche.csb \
--to=fche@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=robertsong.japan@gmail.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