From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14902 invoked by alias); 24 Apr 2012 15:05:05 -0000 Received: (qmail 14892 invoked by uid 22791); 24 Apr 2012 15:05:03 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,FROM_12LTRDOM,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Apr 2012 15:04:50 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1SMhIQ-0005Wc-8S from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Tue, 24 Apr 2012 08:04:50 -0700 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 24 Apr 2012 08:04:49 -0700 Received: from localhost.localdomain (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.1.289.1; Tue, 24 Apr 2012 08:04:48 -0700 From: Yao Qi To: Subject: [PATCH] Document board settting Date: Tue, 24 Apr 2012 15:05:00 -0000 Message-ID: <1335279956-7548-1-git-send-email-yao@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes 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: 2012-04/txt/msg00782.txt.bz2 This patch is to describe all the existing board settings we are using in GDB testsuite. Some of them are obvious, but some are not. I referred CVS log and mail archives to get the description to each of them. I comment out gdb,noresults and use_cygmon, which I can't figure out the purpose of using them. I'll figure them out later. Please pay attention to my explanation to "gdb,nofileio" and "gdb,noinferiorio". I am not satisfied with them, but unable to tell the difference of them. gdb/doc: 2012-04-24 Yao Qi * gdbint.texinfo (Testsuite): New section `Board settings'. --- gdb/doc/gdbint.texinfo | 56 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 56 insertions(+), 0 deletions(-) diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index fcc106c..80196b8 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -7873,6 +7873,62 @@ gdb_test "python print ttype.template_argument(2)" "&C::c" @end smallexample @end table +@section Board settings +In @value{GDBN} testsuite, the tests can be configured or customized in its board +file by means of @dfn{Boarding Settings}. Here are the board settings, + +@table @code + +@item gdb,cannot_call_functions +Whether the board supports inferior call, that is, invoking inferior functions +in @value{GDBN}. If inferior call is required in test case, this variable +should be checked. +@item gdb,can_reverse +Whether the board supports reverse execution. If reverse execution is required +in test case, this variable should be checked. +@item gdb,no_hardware_watchpoints +Whether the board supports hardware watchpoints. If hardware watchpoints +are required in test case, this variable should be checked. +@item gdb,nofileio +Whether the remote stub intercept target file operations and perform them on +the host. +@item gdb,noinferiorio +Whether the inferior has I/O capability on the board. If test case has to do +some operations related to I/O, such as printing, this variable should be +checked. +@c @item gdb,noresults +@c NEED DOCUMENT. +@item gdb,nosignals +Whether signals are supported on target board. If test case uses signals, +this variable should be checked. +@item gdb,skip_huge_test +Whether to skip time-consuming tests on the board with slow connection. If +test case is time-consuming, this variable should be checked. +@item gdb,skip_float_tests +Whether to skip tests related to float points on target board. If the test +cases use floating points, this variable should be checked. +@item gdb,use_precord +Whether support process record on target board. If the test case use target +record, this variable should be checked. +@item gdb_server_prog +The location of GDBserver. If GDBserver somewhere other than its default +location is used in test, specify the location of GDBserver in this variable. +@item in_proc_agent +The location of in-process agent. If in-process agent other than its default +location is used in test, specify the location of in-process agent in +this variable. +@item noargs +Whether configuration of @value{GDBN} supports argument passing for inferior. +If the test case needs argument passing, this variable should be checked. +@item no_long_long +Whether target board supports type @code{long long}. If test case uses +@code{long long}, this variable should be checked. +@c @item use_cygmon +@c NEED DOCUMENT. +@item use_gdb_stub +Whether the tests are running with gdb stub. +@end table + @node Hints @chapter Hints -- 1.7.0.4