From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9567 invoked by alias); 25 May 2009 19:20:07 -0000 Received: (qmail 9558 invoked by uid 22791); 25 May 2009 19:20:06 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from e24smtp05.br.ibm.com (HELO e24smtp05.br.ibm.com) (32.104.18.26) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 25 May 2009 19:20:00 +0000 Received: from mailhub1.br.ibm.com (mailhub1.br.ibm.com [9.18.232.109]) by e24smtp05.br.ibm.com (8.13.1/8.13.1) with ESMTP id n4PJIeCa009047 for ; Mon, 25 May 2009 16:18:40 -0300 Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n4PJKK581008024 for ; Mon, 25 May 2009 16:20:20 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n4PJJtMx026693 for ; Mon, 25 May 2009 16:19:56 -0300 Received: from [9.8.6.174] ([9.8.6.174]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n4PJJt7p026683; Mon, 25 May 2009 16:19:55 -0300 Subject: Re: support for BookE hardware debug features From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= To: Thiago Jung Bauermann Cc: gdb ml , Luis Machado In-Reply-To: <1243193918.10406.0.camel@hactar> References: <1236026362.8949.96.camel@localhost.localdomain> <1243193918.10406.0.camel@hactar> Content-Type: text/plain; charset="ISO-8859-1" Date: Mon, 25 May 2009 19:20:00 -0000 Message-Id: <1243279194.24075.15.camel@miki> 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/msg00165.txt.bz2 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. Unfortunately, I don't have much details about this fix, but I think Thiago can explain more (if needed). Also, IIUC, this fix is not related to the job we're doing so we could send it before we're able to send other patches :-). > 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? > Sérgio did most of the work here. I don't know if he wants to add > anything to this report... Thank you, the report is very good! Regards, -- Sérgio Durigan Júnior Linux on Power Toolchain - Software Engineer Linux Technology Center - LTC IBM Brazil