Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com, drow@false.org, mark.kettenis@xs4all.nl
Subject: Re: [RFC] GDB patches for hw watchpoints - revised
Date: Tue, 06 Dec 2005 23:05:00 -0000	[thread overview]
Message-ID: <uslt6km76.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0512061356530.10445@linux.site> (message from Wu 	Zhou on Tue, 6 Dec 2005 14:12:26 +0800 (CST))

> Date: Tue, 6 Dec 2005 14:12:26 +0800 (CST)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> cc: drow@false.org, eliz@gnu.org, mark.kettenis@xs4all.nl
> 
> 3. Eli ever expressed a concern that the PPC doesn't have a way to return 
> the data address that triggered the watchpoint?  As far as I think, the 
> reason is that PPC will only have one DABR (if it does have). So maybe we 
> don't need to have such a method.  

Sorry, I'm not following: no matter how many debug registers the PPC
has, it can still return to GDB the data address that triggered the
watchpoint.  I don't think the higher levels of GDB (breakpoint.c)
should know or assume anything about the target capabilities or
resources.  Let's try keeping the code clean of such peculiarities.


  parent reply	other threads:[~2005-12-06 20:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 19:54 Wu Zhou
2005-12-06 22:46 ` Ulrich Weigand
2005-12-09 12:00   ` Wu Zhou
2005-12-09 14:34     ` Ulrich Weigand
2005-12-06 23:05 ` Eli Zaretskii [this message]
2005-12-06 23:31   ` Daniel Jacobowitz
2005-12-09 12:04     ` Wu Zhou
2005-12-09 14:22       ` Daniel Jacobowitz
2005-12-09 18:58         ` Eli Zaretskii
2005-12-10 22:23         ` Wu Zhou
2005-12-11 11:12           ` Daniel Jacobowitz
2005-12-11 14:39             ` Wu Zhou
2005-12-13 22:47             ` Wu Zhou
2005-12-14 18:12               ` Eli Zaretskii
2005-12-14 18:13               ` Daniel Jacobowitz
2005-12-15 20:06                 ` Wu Zhou
2005-12-16  0:10                   ` Anton Blanchard
2005-12-22 15:26 Wu Zhou
2005-12-22 15:38 ` Wu Zhou
2005-12-22 15:57   ` Eli Zaretskii
2005-12-22 15:57     ` Wu Zhou
2005-12-23 20:52       ` Eli Zaretskii
2006-01-22 20:56       ` Daniel Jacobowitz
2006-01-24  3:40         ` Wu Zhou
2006-01-24  3:43           ` Daniel Jacobowitz
2006-01-24  4:33             ` Wu Zhou
2006-01-24 11:00               ` Wu Zhou
2006-01-24 21:20                 ` Daniel Jacobowitz
2006-01-25  3:19                   ` Wu Zhou
2006-01-25  8:34                     ` Replace to_region_size_ok_for_hw_watchpoint references with to_region_ok_for_hw_watchpoint ones Wu Zhou
2006-02-02  1:43                       ` [RFC] GDB patches for hw watchpoints - revised Daniel Jacobowitz
2006-02-08  5:35                         ` Wu Zhou
2006-02-09  5:44                           ` Wu Zhou
2006-02-09  7:44                             ` Eli Zaretskii
2006-02-13  9:53                               ` Wu Zhou

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=uslt6km76.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --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