From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22550 invoked by alias); 20 Aug 2004 15:07:41 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22506 invoked from network); 20 Aug 2004 15:07:40 -0000 Received: from unknown (HELO maynard.mail.mindspring.net) (207.69.200.243) by sourceware.org with SMTP; 20 Aug 2004 15:07:40 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1ByAzT-0003dZ-00; Fri, 20 Aug 2004 11:07:39 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id 3D6574B102; Fri, 20 Aug 2004 11:08:02 -0400 (EDT) Date: Fri, 20 Aug 2004 15:07:00 -0000 From: Michael Chastain To: schwab@suse.de, eliz@gnu.org Subject: Re: [rfa/doco] Test Suite: build != host Cc: gdb-patches@sources.redhat.com Message-ID: <412613D1.nail1XO16AREJ@mindspring.com> References: <4124776A.nailCD81LG97@mindspring.com> <01c486c5$Blat.v2.2.2$eed2fae0@zahav.net.il> In-Reply-To: <01c486c5$Blat.v2.2.2$eed2fae0@zahav.net.il> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00596.txt.bz2 andreas> IMHO @samp would be the right one. eli> It depends on what "UNRESOLVED" means, exactly. I must confess I eli> don't understand what does it mean "return UNRESOLVED". Is it a eli> literal string printed by the test script, or is it something else? That's right, it's a literal string. Here is an excerpt from a gdb.sum file: Running /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.exp ... gdb compile failed, /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c: In function `main': /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c:39: warning: incompatible implicit declaration of built-in function 'exit' /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c:47: warning: incompatible implicit declaration of built-in function 'exit' WARNING: Testcase compile failed, so all tests in this file will automatically fail. ERROR: (timeout) GDB never initialized after 10 seconds. WARNING: remote_expect statement without a default case?! ERROR: couldn't load /tmp/migbat-testgdb-49vpUkli/test/gdb.base/unload into gdb (end of file). UNRESOLVED: gdb.base/unload.exp: set pending breakpoint FAIL: gdb.base/unload.exp: single pending breakpoint info FAIL: gdb.base/unload.exp: running program FAIL: gdb.base/unload.exp: continuing to end of program FAIL: gdb.base/unload.exp: rerun to shared library breakpoint FAIL: gdb.base/unload.exp: continuing to end of program second time This script, unload.exp, has some WARNING, ERROR, UNRESOLVED, and FAIL results. (The actual bug has already been fixed, I'm just grabbing this excerpt to illustrate UNRESOLVED). My wording is: DejaGNU supports separate build, host, and target machines. However, some @value{GDBN} test scripts do not work if the host machine is separate from the build machine. These scripts will return an UNRESOLVED result in such an environment. I'm open to alternate wording, and I'm definitely open to improving the markup.