This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Extra diagnostic for tests

From: "Michael Snyder" <Michael dot Snyder at palmsource dot com>
To: "Mark Kettenis" <mark dot kettenis at xs4all dot nl>, <vladimir at codesourcery dot com>
Cc: <gdb-patches at sources dot redhat dot com>
Date: Wed, 13 Sep 2006 10:53:36 -0700
Subject: RE: Extra diagnostic for tests
References: <200609131352.16082.vladimir@codesourcery.com> <200609131018.k8DAI1rt026498@elgar.sibelius.xs4all.nl>

Yeah, but it's possible to run the testsuite somewhere other than the build tree.


-----Original Message-----
From: gdb-patches-owner@sourceware.org on behalf of Mark Kettenis
Sent: Wed 9/13/2006 3:18 AM
To: vladimir@codesourcery.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Extra diagnostic for tests
 
> From: Vladimir Prus <vladimir@codesourcery.com>
> 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.

Mark

References:
- Extra diagnostic for tests
  - From: Vladimir Prus
- Re: Extra diagnostic for tests
  - From: Mark Kettenis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]