Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: jrydberg@virtutech.com, drow@false.org, gdb@sources.redhat.com
Subject: Re: read watchpoints ignored?
Date: Tue, 15 Nov 2005 04:01:00 -0000	[thread overview]
Message-ID: <uhdaeimpv.fsf@gnu.org> (raw)
In-Reply-To: <200511141642.22179.ghost@cs.msu.su> (message from Vladimir Prus on Mon, 14 Nov 2005 16:42:20 +0300)

> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Mon, 14 Nov 2005 16:42:20 +0300
> Cc: Daniel Jacobowitz <drow@false.org>,
>  Eli Zaretskii <eliz@gnu.org>,
>  gdb@sources.redhat.com
> 
> This essentially disables read watchpoints. What's the point in first 
> implementing read watchpoints in a target, and then disabling them completely 
> in gdb?

I agree, this is not a good solution.

> I don't yet have specific *real-world* examples, but using "is the value 
> different from the value last time we stopped" as a heuristic to decide if we 
> hit write watchpoint or read watchpoint seems fragile.

It is a vast improvement on what we had before.


      parent reply	other threads:[~2005-11-15  4:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 13:22 Vladimir Prus
2005-11-11 18:19 ` Eli Zaretskii
2005-11-13 16:45   ` Daniel Jacobowitz
2005-11-13 22:38     ` Eli Zaretskii
2005-11-14  2:43       ` Daniel Jacobowitz
2005-11-14  4:38         ` Eli Zaretskii
2005-11-14 14:42           ` Daniel Jacobowitz
2005-11-15  4:02             ` Eli Zaretskii
2005-11-14 10:10         ` Vladimir Prus
2005-11-14 14:41           ` Daniel Jacobowitz
2005-11-14 14:45             ` Daniel Jacobowitz
2005-11-15  4:02               ` Eli Zaretskii
2005-11-14 13:16         ` Johan Rydberg
2005-11-14 13:42           ` Vladimir Prus
2005-11-14 13:59             ` Johan Rydberg
2005-11-14 14:10               ` Vladimir Prus
2005-11-15  4:01             ` 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=uhdaeimpv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=jrydberg@virtutech.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