From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5313 invoked by alias); 18 Dec 2007 00:48:40 -0000 Received: (qmail 5304 invoked by uid 22791); 18 Dec 2007 00:48:39 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Dec 2007 00:48:25 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 1909398129; Tue, 18 Dec 2007 00:48:24 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id EF27D98100; Tue, 18 Dec 2007 00:48:23 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1J4QdD-0007vd-6u; Mon, 17 Dec 2007 19:48:23 -0500 Date: Tue, 18 Dec 2007 00:48:00 -0000 From: Daniel Jacobowitz To: Siva Velusamy Cc: gdb@sourceware.org Subject: Re: rwatchpoint configuration Message-ID: <20071218004823.GA30270@caradoc.them.org> Mail-Followup-To: Siva Velusamy , gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) 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/msg00126.txt.bz2 On Mon, Dec 17, 2007 at 04:42:51PM -0800, Siva Velusamy wrote: > gdb/breakpoint.c:2792 > > case WP_VALUE_CHANGED: > if (b->type == bp_read_watchpoint) > { > /* Don't stop: read watchpoints shouldn't fire if > the value has changed. This is for targets > which cannot set read-only watchpoints. */ > bs->print_it = print_it_noop; > bs->stop = 0; > continue; > } > > Since the MicroBlaze target can indeed set read-only watchpoints, this > should not happen. It looks as if the target has not been properly > configured. Could someone point me to the appropriate configuration > settings and what the correct values should be for a processor that > natively supports read watchpoints? I don't think there is an appropriate configuration knob at present. Eli, I think I remember you discussing this with someone else, a year or two ago; do you remember the reasoning? If the watchpoint's type is "only trigger on reads", then core GDB assuming it triggers on all accesses seems problematic to me. -- Daniel Jacobowitz CodeSourcery