This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA/doco/testsuite] Document new gdb_test_timeout global variable.
> Date: Tue, 9 Feb 2010 17:10:15 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > > +If not specifically defined, this variable gets automatically defined
> > > +to the same value as @code{timeout} during the testsuite initialization
> > > +(the actual value depends on the exact running parameters).
> >
> > It would be worth saying more about how to find out the default
> > value. If I'm a reader of this section, I might ask myself whether I
> > need to set the variable to a non-default value, but it is impossible
> > to answer that question without knowing what would be the value if I
> > don't do anything.
>
> The problem is that this is tricky and really depends a lot on whether
> the user uses a board file or not, since dejagnu is so configurable
> (you should see the list of files that get loaded at startup). I'm not
> even certain that *I* know the entire story: As far as I can tell,
> gdb/testsuite/config/unix.exp sets a timeout of 60 seconds. I don't
> think we set the timeout anywhere else. So that leaves the question
> of board files. If the user used board files, then they may or may not
> have also set the timeout there.
How about this?
The default value of the timeout is defined in the file
@file{gdb/testsuite/config/unix.exp} that is part of the
@value{GDBN} test suite@footnote{
If you are using a board file, it could override the test-suite
default; search the board file for "timeout".}.