From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27765 invoked by alias); 14 Nov 2005 13:59:51 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 27739 invoked by uid 22791); 14 Nov 2005 13:59:47 -0000 Received: from dns.vtab.com (HELO gorgon.vtab.com) (62.20.90.195) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 14 Nov 2005 13:59:47 +0000 Received: from [10.0.0.133] (despair.hq.vtech [10.0.0.133]) by gorgon.vtab.com (Postfix) with ESMTP id 9A83FB9174; Mon, 14 Nov 2005 14:59:45 +0100 (CET) Message-ID: <43789851.7080608@virtutech.com> Date: Mon, 14 Nov 2005 13:59:00 -0000 From: Johan Rydberg User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) MIME-Version: 1.0 To: Vladimir Prus Cc: Daniel Jacobowitz , Eli Zaretskii , gdb@sources.redhat.com Subject: Re: read watchpoints ignored? References: <200511111622.01337.ghost@cs.msu.su> <20051114024345.GB10567@nevyn.them.org> <43788E28.90108@virtutech.com> <200511141642.22179.ghost@cs.msu.su> In-Reply-To: <200511141642.22179.ghost@cs.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-11/txt/msg00266.txt.bz2 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