From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] GDBserver self tests
Date: Fri, 11 Aug 2017 17:10:00 -0000 [thread overview]
Message-ID: <68a9119e-208e-a0d7-0733-12896b7fc20b@redhat.com> (raw)
In-Reply-To: <1502465408-24668-4-git-send-email-yao.qi@linaro.org>
On 08/11/2017 04:30 PM, Yao Qi wrote:
>
> 2017-05-26 Yao Qi <yao.qi@linaro.org>
>
> * gdb.server/unittest.exp: New.
This is missing from the patch.
> +* New features in the GDB remote stub, GDBserver
> +
> + ** New "--selftest" command line option runs some GDBserver self
> + tests. These self tests are disabled in release.
"disabled in release mode." or "disabled in releases." ?
> @@ -3357,6 +3359,7 @@ gdbserver_usage (FILE *stream)
> " Options:\n"
> " vCont, Tthread, qC, qfThreadInfo and \n"
> " threads (disable all threading packets).\n"
> + " --selftest Run self tests.\n"
> "\n"
> "For more information, consult the GDB manual (available as on-line \n"
> "info or a printed manual).\n");
I wonder whether "gdbserver --help" should really advertise --selftests,
given it's a maintenance command and essentially does nothing in
release mode.
> +@cindex @option{--selftest}
> +The @option{--wrapper} option runs the self tests in @code{gdbserver}:
> +
Pasto: "--wrapper" should be "--selftest".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-08-11 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 15:31 [PATCH 0/3] Use selftest.c in GDBserver Yao Qi
2017-08-11 15:31 ` [PATCH 3/3] GDBserver self tests Yao Qi
2017-08-11 16:01 ` Eli Zaretskii
2017-08-11 17:10 ` Pedro Alves [this message]
2017-08-18 8:16 ` Yao Qi
2017-08-11 15:31 ` [PATCH 2/3] Remove some GDB specific stuff from selftest.c Yao Qi
2017-08-11 15:31 ` [PATCH 1/3] Put selftests api into selftests namespace Yao Qi
2017-08-11 17:11 ` [PATCH 0/3] Use selftest.c in GDBserver Pedro Alves
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=68a9119e-208e-a0d7-0733-12896b7fc20b@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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