From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28584 invoked by alias); 18 Dec 2007 04:23:14 -0000 Received: (qmail 28576 invoked by uid 22791); 18 Dec 2007 04:23:13 -0000 X-Spam-Check-By: sourceware.org Received: from heller.inter.net.il (HELO heller.inter.net.il) (213.8.233.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Dec 2007 04:23:07 +0000 Received: from HOME-C4E4A596F7 (IGLD-84-229-203-142.inter.net.il [84.229.203.142]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id EJR63071 (AUTH halo1); Tue, 18 Dec 2007 06:23:01 +0200 (IST) Date: Tue, 18 Dec 2007 04:23:00 -0000 Message-Id: From: Eli Zaretskii To: "Siva Velusamy" CC: gdb@sourceware.org In-reply-to: (siva.velusamy@gmail.com) Subject: Re: rwatchpoint configuration Reply-to: Eli Zaretskii References: <20071218004823.GA30270@caradoc.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00132.txt.bz2 > Date: Mon, 17 Dec 2007 16:59:39 -0800 > From: "Siva Velusamy" > > In this thread: > > http://sources.redhat.com/ml/gdb/2005-11/msg00251.html > > Eli mentions that "If someone finds a way to announce a read > watchpoint when the value changed on a target that supports that, > without losing support for read watchpoints on x86 (which is by far > the most popular platform these days), I'll gladly agree to such a > change" > > So I guess the question really is if there has been an update to this. For now, you could try a workaround: put two watchpoints on the same expression: one an rwatch (the one you wanted), the other a write watchpoint whose `commands' say just "continue". This should cause GDB to note the changed value when it is written into the variable(s), so when the rwatch triggers it will see the known value and stop. Please see if this works for you. If it doesn't, please tell more details.