From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 859 invoked by alias); 11 Feb 2010 07:52:38 -0000 Received: (qmail 851 invoked by uid 22791); 11 Feb 2010 07:52:37 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Feb 2010 07:52:33 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 8A8E72BAAE1; Thu, 11 Feb 2010 02:52:31 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pCrfKT5snsV6; Thu, 11 Feb 2010 02:52:31 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 049362BAB83; Thu, 11 Feb 2010 02:52:30 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 82E09F59AE; Thu, 11 Feb 2010 11:52:23 +0400 (RET) Date: Thu, 11 Feb 2010 07:52:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [RFA/doco/testsuite] Document new gdb_test_timeout global variable. Message-ID: <20100211075223.GB2907@adacore.com> References: <1265631452-2476-1-git-send-email-brobecker@adacore.com> <83eikvegcs.fsf@gnu.org> <20100209131015.GH16325@adacore.com> <836366dzd0.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <836366dzd0.fsf@gnu.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-02/txt/msg00280.txt.bz2 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 360 > How about this? Works for me! Thanks for the suggestion. Attached is the new version. I moved up a bit the paragraph explaining why this global variable might be useful - I felt it was nicer and more natural to have it before explaining what the default value was, and where to find it. But I can move it back. OK to commit this version? Thanks, -- Joel --gBBFr7Ir9EOA20Yy Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="doc-gdb-test-timeout.diff" Content-length: 2011 commit bdb6c0007cdba70be6f48515823368aca6dc8eee Author: Joel Brobecker Date: Mon Feb 8 16:11:28 2010 +0400 [testsuite] Document new gdb_test_timeout global variable. gdb/doc/ChangeLog: * gdbint.texinfo (Testsuite): New section "Testsuite Configuration", documenting the gdb_test_timeout variable. diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index c90af05..7c3fb7e 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -7693,6 +7693,38 @@ make site.exp runtest TRANSCRIPT=y @end smallexample +@section Testsuite Configuration +@cindex Testsuite Configuration + +It is possible to adjust the behavior of the testsuite by defining +the global variables listed below, either in a @file{site.exp} file, +or in a @file{board} file. + +@itemize @bullet + +@item @code{gdb_test_timeout} + +Defining this variable changes the default timeout duration used during +communication with @value{GDBN}. More specifically, the global variable +used during testing is @code{timeout}, but this variable gets reset to +@code{gdb_test_timeout} at the beginning of each testcase, making sure +that any local change to @code{timeout} in a testcase does not affect +subsequent testcases. + +This global variable comes in handy when the debugger is slower than +normal due to the testing environment, triggering unexpected @code{TIMEOUT} +test failures. Examples include when testing on a remote machine, or +against a system where communications are slow. + +If not specifically defined, this variable gets automatically defined +to the same value as @code{timeout} during the testsuite initialization. +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".}. + +@end itemize + @section Testsuite Organization @cindex test suite organization --gBBFr7Ir9EOA20Yy--