From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2366 invoked by alias); 18 Dec 2007 00:43:01 -0000 Received: (qmail 2348 invoked by uid 22791); 18 Dec 2007 00:43:00 -0000 X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.185) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Dec 2007 00:42:54 +0000 Received: by nf-out-0910.google.com with SMTP id b11so1407796nfh.48 for ; Mon, 17 Dec 2007 16:42:52 -0800 (PST) Received: by 10.78.165.16 with SMTP id n16mr9414448hue.63.1197938571765; Mon, 17 Dec 2007 16:42:51 -0800 (PST) Received: by 10.78.132.4 with HTTP; Mon, 17 Dec 2007 16:42:51 -0800 (PST) Message-ID: Date: Tue, 18 Dec 2007 00:43:00 -0000 From: "Siva Velusamy" To: gdb@sourceware.org Subject: rwatchpoint configuration MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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/msg00125.txt.bz2 Hello, I am debugging a read watchpoint issue on an embedded target (Xilinx MicroBlaze processor). The issue I'm trying to resolve is that gdb breaks on a read watchpoint _only_ if the value of the variable being watched has not changed since the watchpoint was set. This comes from the following condition in gdb: 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? Note that read watchpoints do work fine if the value has not changed since the breakpoint was set. Also, the serial protocol packet received looks like "T05watch:000014ec;" in one specific test when the read watchpoint is hit. Thanks, Siva -- In the end, everything is a gag. Charlie Chaplin