From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Xin Tong <xerox.time.tech@gmail.com>
Cc: "Gustavo, Luis" <luis_gustavo@mentor.com>, gdb@sourceware.org
Subject: Re: Hardware watchpoint for read
Date: Thu, 03 May 2012 21:18:00 -0000 [thread overview]
Message-ID: <1336079874.23991.6.camel@soleil> (raw)
In-Reply-To: <CALKntY1qTnXd1g2dEXzitTWH6Q2zD5HNu2NaAvfk7GaME=JjVw@mail.gmail.com>
On Thu, 2012-05-03 at 15:41 -0400, Xin Tong wrote:
> The breakpoint instructions (int 3 on x86) are inserted in the
> translation process ?
Valgrind gdbserver implements breakpoints during code translation
by inserting calls to a Valgrind "helper" procedure.
You can use a Valgrind gdbserver monitor command to inspect
the translation:
v.translate <addr> [<traceflags>] : debug translation of <addr> with <traceflags>
(default traceflags 0b00100000 : show after instrumentation)
An additional flag 0b100000000 allows to show gdbserver instrumentation
read/write/access watchpoints are implemented on top of memcheck
"addressability" V bits. memcheck is the only Valgrind tool that
implements watchpoints.
Philippe
prev parent reply other threads:[~2012-05-03 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 13:03 Xin Tong
2012-04-24 13:09 ` Luis Gustavo
2012-04-24 13:16 ` Xin Tong
2012-04-24 13:18 ` Luis Gustavo
2012-04-24 14:18 ` Xin Tong
2012-04-24 14:20 ` Luis Gustavo
2012-04-24 15:06 ` Xin Tong
2012-04-24 15:11 ` Luis Gustavo
2012-04-25 1:15 ` Xin Tong
2012-04-25 11:51 ` Luis Gustavo
2012-05-03 19:19 ` Philippe Waroquiers
2012-05-03 19:41 ` Xin Tong
2012-05-03 21:18 ` Philippe Waroquiers [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=1336079874.23991.6.camel@soleil \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=luis_gustavo@mentor.com \
--cc=xerox.time.tech@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).