From: Wu Zhou <woodzltc@cn.ibm.com>
To: gdb-patches@sourceware.org
Subject: [ppc-linux-nat]: set access flag for h/w watchpoint even if it is only read or write
Date: Fri, 09 Jun 2006 15:40:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0606092320510.5286@localhost.localdomain> (raw)
Hello all,
I found a bug in the current ppc-linux h/w watchpoint implementation:
when we set read watchpoint to some expression, if there are any write
operation to it before a read operation is hit, watchpoint_check will see
that its value is changed. So user won't see the watchpoint is hit.
I make one change to the SET_DEBUGREG operation: even if it is only
read or write watchpoint, we still set access flag. Then, no matter
what operation is on the watched address, a SIGTRAP will be triggered.
The gdb code itself can determine if it is a write operation or read
operation. If it is write, watchpoint_check routine can update the
bs->value to the latest.
Here is the patch. Thanks for reviewing.
2006-06-09 Wu Zhou <woodzltc@cn.ibm.com>
* ppc-linux-nat.c (ppc_linux_insert_watchpoint): Set access flag for
all hardware watchpoint.
--- ppc-linux-nat.c.orig 2006-06-09 14:53:35.000000000 +0800
+++ ppc-linux-nat.c 2006-06-09 15:04:12.000000000 +0800
@@ -821,22 +821,7 @@ ppc_linux_insert_watchpoint (CORE_ADDR a
long dabr_value;
ptid_t ptid = inferior_ptid;
- dabr_value = addr & ~7;
- switch (rw)
- {
- case hw_read:
- /* Set read and translate bits. */
- dabr_value |= 5;
- break;
- case hw_write:
- /* Set write and translate bits. */
- dabr_value |= 6;
- break;
- case hw_access:
- /* Set read, write and translate bits. */
- dabr_value |= 7;
- break;
- }
+ dabr_value = addr | 7;
tid = TIDGET (ptid);
if (tid == 0)
:ADDPATCH ppc:
Regards
- Wu Zhou
next reply other threads:[~2006-06-09 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 15:40 Wu Zhou [this message]
2006-06-23 0:44 ` [RFC]: h/w watchpoint (r,w,a) for ppc440 Wu Zhou
2006-07-06 13:20 ` [ppc-linux-nat]: set access flag for h/w watchpoint even if it is only read or write Daniel Jacobowitz
2006-07-06 20:59 ` Eli Zaretskii
2006-07-06 21:37 ` Daniel Jacobowitz
2006-07-07 4:35 Wu Zhou
2006-07-07 10:04 ` Eli Zaretskii
2006-07-07 13:18 ` Daniel Jacobowitz
2006-07-07 15:08 ` Eli Zaretskii
2006-07-08 19:36 ` Ulrich Weigand
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=Pine.LNX.4.64.0606092320510.5286@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=gdb-patches@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