From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26524 invoked by alias); 4 Feb 2004 22:49:10 -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 26517 invoked from network); 4 Feb 2004 22:49:10 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 4 Feb 2004 22:49:10 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 451B72B92; Wed, 4 Feb 2004 17:49:08 -0500 (EST) Message-ID: <402176E4.5080902@gnu.org> Date: Wed, 04 Feb 2004 22:49:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com Subject: Re: Problems with dejagnu and c++ tests... References: <20040204223104.7766C4B364@berman.michael-chastain.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00085.txt.bz2 > ac> Something based on CPP would be more robust, and avoid assumptions such > ac> as the target has output and can correctly compile / execute code. > ac> Consider what happens when trying to bring up a new GDB+GCC+.... > > We're running the test suite. If gdb_compile does not work, > or the resulting executables cannot be run, then the test script > cannot run its tests anyways. Which would mean that a GCC code-gen bug in malloc, or printf would block all ability to run the testsuite :-( We need to avoid making the testsuite fragile. Andrew