From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7212 invoked by alias); 26 May 2009 14:28:49 -0000 Received: (qmail 7201 invoked by uid 22791); 26 May 2009 14:28:47 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from e24smtp01.br.ibm.com (HELO e24smtp01.br.ibm.com) (32.104.18.85) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 26 May 2009 14:28:40 +0000 Received: from mailhub1.br.ibm.com (mailhub1.br.ibm.com [9.18.232.109]) by e24smtp01.br.ibm.com (8.13.1/8.13.1) with ESMTP id n4QEmdCJ017252 for ; Tue, 26 May 2009 11:48:39 -0300 Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n4QESvfd1007940 for ; Tue, 26 May 2009 11:28:58 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n4QESXta002036 for ; Tue, 26 May 2009 11:28:33 -0300 Received: from [9.8.7.149] ([9.8.7.149]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n4QESWDm001961; Tue, 26 May 2009 11:28:32 -0300 Subject: Re: support for BookE hardware debug features From: Thiago Jung Bauermann To: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= Cc: gdb ml , Luis Machado In-Reply-To: <1243279194.24075.15.camel@miki> References: <1236026362.8949.96.camel@localhost.localdomain> <1243193918.10406.0.camel@hactar> <1243279194.24075.15.camel@miki> Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 May 2009 14:28:00 -0000 Message-Id: <1243348109.26330.1.camel@hactar> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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: 2009-05/txt/msg00166.txt.bz2 Em Seg, 2009-05-25 às 16:19 -0300, Sérgio Durigan Júnior escreveu: > On Sun, 2009-05-24 at 16:38 -0300, Thiago Jung Bauermann wrote: > > > I implemented a "watch-range" command, which takes a start address (or > > expression which evaluates to an address) and an end address (or > > expression). Not sure if I'll keep it that way or change. Didn't think > > much about it yet. > > Just to complement (I don't know if it's worth mentioning, but > anyway...) it seems we may have found a little bug regarding > watchpoint's expression evaluation. Basically, the problem was > occurring when GDB tried to see if a block of memory changed in order to > determine whether it should trigger the watchpoint. GDB was basically > comparing the address of this memory region, and not the content itself, > which made it impossible to trigger the watchpoint. Indeed. I was meaning to submit the fix as a separate patch, but I forgot. Will regression test it and submit the fix ASAP. > > We are just starting to work on the DVC (conditioned hw watchpoint), but > > for now I'm inclined to use it automagically for simple expressions with > > just one == or != operator. We're taking into account Joel's comments > > and suggestions on this. Thanks Joel for your input! > > That is what I was thinking, too. I don't know if it's possible to use > the DVC registers for more complex expressions, do you? I think not, but I may be wrong. As we get more familiar with the hardware feature, we'll see. -- []'s Thiago Jung Bauermann IBM Linux Technology Center