From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Jimmy Guo <guo@cup.hp.com>
Cc: gdb@sourceware.cygnus.com, "Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: gdb.gdbtk tests
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-ID: <38DAA014.780BE4BD@cygnus.com>
References: <Pine.LNX.4.10.10003231245280.9146-100000@hpcll168.cup.hp.com>
X-SW-Source: 2000-q1/msg00779.html
Message-ID: <20000401000000.FufKvzKAK3qI6gBrLgZnyWJ3K2ecyFJpfWFjpoZ_LGo@z>

Jimmy Guo wrote:
> 
> These tests apparently require top level tk/, tix/, itcl/, and libgui/
> (the Cygnus GUI) components be present in the source tree (per
> gdb/testsuite/lib/gdb.exp (gdbtk_start)).  Will these components be part
> of public tree any time soon?

They are already available.  Either download the insight+dejagnu
snapshot or checkout the module ``insight''.

> Besides, it's better to have a sanity check routine testing all
> dependencies before even trying gdb_compile, like the skip_hp_tests one.
>
> Some codes like below will be better:
> 
> set path [file join <whatever path>]
> if ![file isdirectory $path] {
>    perror <error message>
>    return 1 (or exit 1)
> }

The ``GDB'' module doesn't include the gdb.gdbtk testsuites.  However,
given that it's pretty easy to end up with that directory, a more robust
test would be better.

The MI testsuite checks that the GDB binary.

	enjoy,
		Andrew