From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12577 invoked by alias); 14 Jul 2008 15:45:29 -0000 Received: (qmail 12566 invoked by uid 22791); 14 Jul 2008 15:45:28 -0000 X-Spam-Check-By: sourceware.org Received: from igw3.br.ibm.com (HELO igw3.br.ibm.com) (32.104.18.26) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 15:45:03 +0000 Received: from mailhub3.br.ibm.com (unknown [9.18.232.110]) by igw3.br.ibm.com (Postfix) with ESMTP id 4C3433901F4 for ; Mon, 14 Jul 2008 12:26:59 -0300 (BRST) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m6EFj2JZ3367104 for ; Mon, 14 Jul 2008 12:45:02 -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 m6EFivk1020803 for ; Mon, 14 Jul 2008 12:44:57 -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 m6EFitMK020767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Jul 2008 12:44:55 -0300 Subject: (maybe) Async mode failures on PPC From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: gdb@sourceware.org Content-Type: text/plain Date: Mon, 14 Jul 2008 15:45:00 -0000 Message-Id: <1216050287.2607.10.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/msg00153.txt.bz2 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