From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18268 invoked by alias); 16 Sep 2010 14:56:35 -0000 Received: (qmail 18253 invoked by uid 22791); 16 Sep 2010 14:56:33 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD 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; Thu, 16 Sep 2010 14:56:26 +0000 Received: from mailhub1.br.ibm.com (mailhub1.br.ibm.com [9.18.232.109]) by e24smtp01.br.ibm.com (8.14.4/8.13.1) with ESMTP id o8GF6vdq014152 for ; Thu, 16 Sep 2010 12:06:57 -0300 Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.8.31.93]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o8GF27hC340304 for ; Thu, 16 Sep 2010 12:02:08 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id o8GEu0a6027714 for ; Thu, 16 Sep 2010 11:56:00 -0300 Received: from [9.18.235.138] (dyn531401.br.ibm.com [9.18.235.138]) by d24av02.br.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id o8GEu0Ga027696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2010 11:56:00 -0300 Subject: Assumptions on the number of hw watchpoints for some testcases From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" Date: Thu, 16 Sep 2010 14:56:00 -0000 Message-ID: <1284648970.2721.9.camel@gargoyle> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: 2010-09/txt/msg00096.txt.bz2 Hi, Recently i've noticed that some of the newer watchpoint-related (watchpoint.exp, watchthreads.exp and local-watch-wrong-thread.exp for example) testcases were failing due to the testcases themselves not respecting the fact that PPC server processors only have a single HW watchpoint register. Some of the testcases check for "watch *0x0" as a means to tell if the platform actually supports doing "watch *var" in HW. That doesn't work correctly on PPC server processors since "watch *0x0" will use a HW watchpoint and "watch *var" will fall back to two SW watchpoints... I may declare watchthreads.exp unsupported for PPC server as it has a strong assumption that the target can do 2 HW watchpoints or i can write a different testcase relying on a single HW watchpoint. As for the others, i'll try to make the tests more flexible. I don't think GDB has a handy maint command to tell the testcases how many HW watches a target can use. Regards, Luis