From: Eli Zaretskii <eliz@gnu.org>
To: Wu Zhou <woodzltc@cn.ibm.com>, gdb-patches@sourceware.org
Subject: Re: Fw: [ppc-linux-nat]: set access flag for h/w watchpoint even if it is only read or write (fwd)
Date: Thu, 13 Jul 2006 03:21:00 -0000 [thread overview]
Message-ID: <ufyh6mbp9.fsf@gnu.org> (raw)
In-Reply-To: <20060712182958.GA27342@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 12 Jul 2006 14:29:58 -0400)
> Date: Wed, 12 Jul 2006 14:29:58 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Wu Zhou <woodzltc@cn.ibm.com>, gdb-patches@sourceware.org
>
> Right now the i386 target says "you asked me to insert a read
> watchpoint. OK! I've done it" and sneakily inserts an access
> watchpoint instead. That means higher layers can't tell that it's
> going to fire unexpectedly.
>
> If the i386 target instead said "Sorry, I can't insert a read
> watchpoint" and the higher layer said "well, how about this - can
> you insert an access watchpoint?" then it would be able to handle and
> skip the unexpected firing.
I don't mind this change. Thanks for explaining it.
prev parent reply other threads:[~2006-07-13 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF40F802D1.E1DA610C-ON482571A8.004F44D3-482571A8.004F3DA7@cn.ibm.com>
2006-07-11 15:09 ` Wu Zhou
2006-07-12 17:31 ` Daniel Jacobowitz
2006-07-12 18:15 ` Eli Zaretskii
2006-07-12 18:30 ` Daniel Jacobowitz
2006-07-13 3:21 ` Eli Zaretskii [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=ufyh6mbp9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=woodzltc@cn.ibm.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