From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5475 invoked by alias); 14 Jul 2008 16:58:12 -0000 Received: (qmail 5466 invoked by uid 22791); 14 Jul 2008 16:58:11 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 16:57:54 +0000 Received: (qmail 16884 invoked from network); 14 Jul 2008 16:57:52 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 14 Jul 2008 16:57:52 -0000 From: Pedro Alves To: gdb@sourceware.org, luisgpm@linux.vnet.ibm.com Subject: Re: (maybe) Async mode failures on PPC Date: Mon, 14 Jul 2008 16:58:00 -0000 User-Agent: KMail/1.9.9 References: <1216050287.2607.10.camel@gargoyle> <1216053102.2607.13.camel@gargoyle> In-Reply-To: <1216053102.2607.13.camel@gargoyle> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807141757.51890.pedro@codesourcery.com> 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/msg00167.txt.bz2 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. :-( 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. -- Pedro Alves