From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: [committed] : [PATCH] Document board settting
Date: Wed, 25 Apr 2012 11:27:00 -0000 [thread overview]
Message-ID: <4F97DA04.5060707@codesourcery.com> (raw)
In-Reply-To: <837gx4f7o8.fsf@gnu.org>
On 04/25/2012 06:05 PM, Eli Zaretskii wrote:
>> Date: Wed, 25 Apr 2012 17:03:19 +0800
>> From: Yao Qi <yao@codesourcery.com>
>> CC: <gdb-patches@sourceware.org>
>>
>> +@section Board settings
>> +In @value{GDBN} testsuite, the tests can be configured or customized in the board
>> +file by means of @dfn{Board Settings}. Here are the supported board settings:
>> +
>> +If the feature which is about the board setting variable is required in test
>> +cases, the corresponding board setting variable should be checked in test cases.
>
> This should be before the sentence saying "Here are the supported
> board settings". Like this:
>
> In @value{GDBN} testsuite, the tests can be configured or customized
> in the board file by means of @dfn{Board Settings}. Each setting
> should be consulted by test cases that depend on the corresponding
> feature.
>
> Here are the supported board settings:
>
> The
>> +location can be either the full file name of GDBserver, or the path relative to
>> +testsuite directory in build dir.
>
> Suggest a slight rewording:
>
> The location is a file name of GDBserver that can be either absolute or
> relative to the testsuite subdirectory of the build directory.
>
>> +@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. The location can be either the full file name or the path relate
>> +to testsuite directory in build dir.
>
> Same here.
>
> OK with those changes.
>
This is what I committed.
http://sourceware.org/ml/gdb-cvs/2012-04/msg00201.html
--
Yao (é½å°§)
gdb/doc:
2012-04-25 Yao Qi <yao@codesourcery.com>
* gdbint.texinfo (Testsuite): New section `Board settings'.
---
gdb/doc/gdbint.texinfo | 51 ++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 51 insertions(+), 0 deletions(-)
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index fcc106c..267a6eb 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -7873,6 +7873,57 @@ 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 the board
+file by means of @dfn{Board Settings}. Each setting should be consulted by
+test cases that depend on the corresponding feature.
+
+Here are the supported board settings:
+
+@table @code
+
+@item gdb,cannot_call_functions
+The board does not support inferior call, that is, invoking inferior functions
+in @value{GDBN}.
+@item gdb,can_reverse
+The board supports reverse execution.
+@item gdb,no_hardware_watchpoints
+The board does not support hardware watchpoints.
+@item gdb,nofileio
+@value{GDBN} is unable to intercept target file operations in remote and perform
+them on the host.
+@item gdb,noinferiorio
+The board is unable to provide I/O capability to the inferior.
+@c @item gdb,noresults
+@c NEED DOCUMENT.
+@item gdb,nosignals
+The board does not support signals.
+@item gdb,skip_huge_test
+Skip time-consuming tests on the board with slow connection.
+@item gdb,skip_float_tests
+Skip tests related to float points on target board.
+@item gdb,use_precord
+The board supports process record.
+@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.
+The location is a file name of GDBserver that can be either absolute or
+relative to testsuite subdirectory in build directory.
+@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. The location is a file name of in-process agent that can be
+either absolute or relative to testsuite subdirectory in build directory.
+@item noargs
+@value{GDBN} does not support argument passing for inferior.
+@item no_long_long
+The board does not support type @code{long long}.
+@c @item use_cygmon
+@c NEED DOCUMENT.
+@item use_gdb_stub
+The tests are running with gdb stub.
+@end table
+
@node Hints
@chapter Hints
--
1.7.0.4
prev parent reply other threads:[~2012-04-25 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 15:05 Yao Qi
2012-04-24 16:07 ` Yao Qi
2012-04-25 6:24 ` Eli Zaretskii
2012-04-25 9:28 ` Yao Qi
2012-04-25 10:47 ` Eli Zaretskii
2012-04-25 11:27 ` Yao Qi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F97DA04.5060707@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox