From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15217 invoked by alias); 14 Jul 2008 16:32:25 -0000 Received: (qmail 15207 invoked by uid 22791); 14 Jul 2008 16:32:25 -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 16:32:01 +0000 Received: from mailhub3.br.ibm.com (mailhub3 [9.18.232.110]) by igw1.br.ibm.com (Postfix) with ESMTP id 724BA32C265 for ; Mon, 14 Jul 2008 13:04:39 -0300 (BRT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m6EGVnA12543738 for ; Mon, 14 Jul 2008 13:31:50 -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 m6EGVht9023334 for ; Mon, 14 Jul 2008 13:31:43 -0300 Received: from [9.8.1.17] ([9.8.1.17]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m6EGVhmV023283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Jul 2008 13:31:43 -0300 Subject: Re: (maybe) Async mode failures on PPC From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: gdb@sourceware.org In-Reply-To: <1216050287.2607.10.camel@gargoyle> References: <1216050287.2607.10.camel@gargoyle> Content-Type: text/plain Date: Mon, 14 Jul 2008 16:32:00 -0000 Message-Id: <1216053102.2607.13.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/msg00165.txt.bz2 Steps to reproduce this failure: 1 - Load the watchpoint.exp test binary into gdb. 2 - start it and next over a few lines. Results: (gdb) start Temporary breakpoint 1 at 0x10000894: file /home/luis/src/gdb/gdb-head/HEAD/gdb/testsuite/gdb.base/watchpoint.c, line 129. Starting program: /home/luis/builds/gdb-head/DFP/gdb/testsuite/gdb.base/watchpoint Temporary breakpoint 1, main () at /home/luis/src/gdb/gdb-head/HEAD/gdb/testsuite/gdb.base/watchpoint.c:129 129 struct1.val = 1; (gdb) watch ptr1 Hardware watchpoint 2: ptr1 (gdb) n During symbol reading, incomplete CFI data; unspecified registers (e.g., r2) at 0x10000894. 130 struct2.val = 2; (gdb) 131 ptr1 = &struct1; (gdb) Target is executing. (gdb) Cannot execute this command while the selected thread is running. (gdb) Cannot execute this command while the selected thread is running. (gdb) Cannot execute this command while the selected thread is running. (gdb) On Mon, 2008-07-14 at 12:44 -0300, Luis Machado wrote: > Hey guys, > > I was giving a shot at the testsuite for PPC and some failures showed > up, related, apparently, to the async mode. > > The pattern is like this, first there's a message informing you that the > "Target is running" and then no other commands will be accepted due to > "Cannot execute this command while the selected thread is running.". > > Is this something we're still addressing or a new problem? Should we > modify the testcase so it becomes async-aware? > > For example, this piece of the watchpoint.exp testcase > > (gdb) PASS: gdb.base/watchpoint.exp: until to ival3 assignment > until^M > Target is executing.^M > (gdb) FAIL: gdb.base/watchpoint.exp: until out of loop > step^M > Cannot execute this command while the selected thread is running.^M > > Regards, > Luis