From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28061 invoked by alias); 13 Sep 2006 12:24:47 -0000 Received: (qmail 28045 invoked by uid 22791); 13 Sep 2006 12:24:46 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 13 Sep 2006 12:24:39 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GNTn7-0001u6-FF; Wed, 13 Sep 2006 08:24:33 -0400 Date: Wed, 13 Sep 2006 12:24:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com Subject: Re: Extra diagnostic for tests Message-ID: <20060913122432.GA7278@nevyn.them.org> Mail-Followup-To: Mark Kettenis , vladimir@codesourcery.com, gdb-patches@sources.redhat.com References: <200609131352.16082.vladimir@codesourcery.com> <200609131018.k8DAI1rt026498@elgar.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609131018.k8DAI1rt026498@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00061.txt.bz2 On Wed, Sep 13, 2006 at 12:18:01PM +0200, Mark Kettenis wrote: > > From: Vladimir Prus > > Date: Wed, 13 Sep 2006 13:52:16 +0400 > > > > Hi, > > at the moment, the dejagnu tests use PATH to find the gdb binary, and don't > > report which gdb binary is used. As result, when running runtest manually on > > one test, one can test with different gdb from the one used by 'make check'. > > There must be something wrong with your setup. I have a gdb somewhere > in my PATH, but I'm damn sure the testsuite picks up the gdb in my > build tree. It does: but I suspect Vlad is using our local testing setup, which actually tests outside of the build directory. The check for ../gdb should be earlier than the path search. We actually run just the testsuite configure script in an empty directory, and 99.9% of tests work from there. Handy when testing prebuilt packages. -- Daniel Jacobowitz CodeSourcery