From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28991 invoked by alias); 14 Jul 2008 17:07:41 -0000 Received: (qmail 28979 invoked by uid 22791); 14 Jul 2008 17:07:40 -0000 X-Spam-Check-By: sourceware.org Received: from igw1.br.ibm.com (HELO igw1.br.ibm.com) (32.104.18.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 17:07:11 +0000 Received: from mailhub1.br.ibm.com (mailhub1 [9.18.232.109]) by igw1.br.ibm.com (Postfix) with ESMTP id 5C8BB32C25D for ; Mon, 14 Jul 2008 13:39:49 -0300 (BRT) 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.0) with ESMTP id m6EH77Sx1085632 for ; Mon, 14 Jul 2008 14:07:10 -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 m6EH71a8014334 for ; Mon, 14 Jul 2008 14:07:02 -0300 Received: from [9.8.1.17] ([9.8.1.17]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m6EH70er014297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Jul 2008 14:07:01 -0300 Subject: Re: (maybe) Async mode failures on PPC From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: Pedro Alves Cc: gdb@sourceware.org In-Reply-To: <200807141757.51890.pedro@codesourcery.com> References: <1216050287.2607.10.camel@gargoyle> <1216053102.2607.13.camel@gargoyle> <200807141757.51890.pedro@codesourcery.com> Content-Type: text/plain Date: Mon, 14 Jul 2008 17:07:00 -0000 Message-Id: <1216055220.2607.18.camel@gargoyle> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 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: 2008-07/txt/msg00168.txt.bz2 Hey Pedro, On Mon, 2008-07-14 at 17:57 +0100, Pedro Alves wrote: > Hi Luis, > > On Monday 14 July 2008 17:31:42, Luis Machado wrote: > > Steps to reproduce this failure: > > > > 1 - Load the watchpoint.exp test binary into gdb. > > 2 - start it and next over a few lines. > > I can't reproduce it on x86 (sync or async), neither with your > recipe or by running the watchpoint.exp test. It seems to be a ppc-specific thing. I forgot to mention that you need to place a watchpoint on variable "ptr1" to trigger this. When no watchpoints are inserted, it runs as expected. And this is sync mode, i did not turn async on, and i presume it's off by default, like it was until recently. > :-( > > The "Target is executing" notice comes from frame.c:get_current_frame. > > I couldn't figure out for sure from your description of the > problem if this only happens in async, or if it happen in sync as well, > but I understood async only. > > Why is GDB trying to get the current frame of an executing > thread, or why does GDB think that the current thread is > executing at this point, if it isn't? > > Can you do a bit of debugging and figure out what is the > code path that ended up triggering the first error? > get_current_frame is called from too many places to be able > to do an educated guess. Yes, sorry. I was just wondering if anyone else was having the same problem and did not provide much info about it. I'll dig into it and will provide the code path for the error as it seems to be a regression. But i feel it's related somehow to watchpoints. Regards, Luis