From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2555 invoked by alias); 23 Apr 2013 09:33:55 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 2544 invoked by uid 89); 23 Apr 2013 09:33:54 -0000 X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL autolearn=ham version=3.3.1 Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 23 Apr 2013 09:33:53 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1UUZbi-0001uM-OL from Luis_Gustavo@mentor.com ; Tue, 23 Apr 2013 02:33:50 -0700 Received: from NA1-MAIL.mgc.mentorg.com ([147.34.98.181]) by svr-orw-fem-01.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 23 Apr 2013 02:33:49 -0700 Received: from [172.30.7.127] ([172.30.7.127]) by NA1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Apr 2013 02:33:49 -0700 Message-ID: <5176557B.2080403@codesourcery.com> Date: Tue, 23 Apr 2013 20:25:00 -0000 From: Luis Machado Reply-To: lgustavo@codesourcery.com User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Pedro Alves CC: "'gdb-patches@sourceware.org'" Subject: Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment References: <516EC58C.5060501@codesourcery.com> <51755821.8020907@codesourcery.com> <51755A5F.3060009@redhat.com> <51756D2B.5050204@redhat.com> <51758960.2090702@redhat.com> In-Reply-To: <51758960.2090702@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-04/txt/msg00704.txt.bz2 Hi, On 04/22/2013 09:02 PM, Pedro Alves wrote: > I hacked GDB some more, and I have further insight. > GDB _is_ to blame. Updated GDB/test hack patch at the bottom. > So GDB is to blame. Fixing this, however, would be a different > story, and doesn't look that simple. > > So the test could work around this by making sure that threads > don't exit until after all watchpoints have been tested. Thanks for the analysis! I modified the testcase to prevent those threads from exitting and fixed the weird identation (i messed it up when copying from another source probably). But, there still seems to be something odd here. When the number of threads is greater than the number of available hardware watchpoints, GDB still seems to miss watchpoint hits. I'm currently trying to narrow this down. Luis