Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Johan Rydberg <jrydberg@virtutech.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Daniel Jacobowitz <drow@false.org>, Eli Zaretskii <eliz@gnu.org>,
	gdb@sources.redhat.com
Subject: Re: read watchpoints ignored?
Date: Mon, 14 Nov 2005 13:59:00 -0000	[thread overview]
Message-ID: <43789851.7080608@virtutech.com> (raw)
In-Reply-To: <200511141642.22179.ghost@cs.msu.su>

Vladimir Prus wrote:

> This essentially disables read watchpoints. What's the point in first 
> implementing read watchpoints in a target, and then disabling them completely 
> in gdb? Should be then disallow "read watchpoint" packet in the remote 
> protocol?

I wouldn't say it disables read watchpoints, since the functionality GDB
provides is exactly that; read watchpoints.  The difference is that it
uses access watchpoints to accomplish this, because a large set of targets
does not support true read watchpoints.

Which is more important; providing the functionality, or providing some
functionality for some targets, but using hardware read watchpoints instead
of hardware access watchpoints?

~j


  reply	other threads:[~2005-11-14 13:59 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 [this message]
2005-11-14 14:10               ` Vladimir Prus
2005-11-15  4:01             ` Eli Zaretskii

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=43789851.7080608@virtutech.com \
    --to=jrydberg@virtutech.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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