public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Fix unittest.exp failure due to 'set debuginfod' addition Date: Sun, 31 Oct 2021 17:35:16 +0000 (GMT) [thread overview] Message-ID: <20211031173516.F061B3857413@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2a8f1f474469bd1a35435deaf5fb0a2ce038071d commit 2a8f1f474469bd1a35435deaf5fb0a2ce038071d Author: Tom Tromey <tom@tromey.com> Date: Sun Oct 31 11:34:06 2021 -0600 Fix unittest.exp failure due to 'set debuginfod' addition The 'set debuginfod' change caused a regression in unittest.exp: Running selftest help_doc_invariants. help doc broken invariant: command 'info set debuginfod' help doc first line is not terminated with a '.' character help doc broken invariant: command 'set debuginfod' help doc first line is not terminated with a '.' character help doc broken invariant: command 'show debuginfod' help doc first line is not terminated with a '.' character Self test failed: self-test failed at ../../binutils-gdb/gdb/unittests/command-def-selftests.c:100 This patch fixes the problem. I'm checking it in. Diff: --- gdb/debuginfod-support.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gdb/debuginfod-support.c b/gdb/debuginfod-support.c index 097977cd45c..a1269772b2e 100644 --- a/gdb/debuginfod-support.c +++ b/gdb/debuginfod-support.c @@ -406,8 +406,8 @@ _initialize_debuginfod () { /* set/show debuginfod */ add_setshow_prefix_cmd ("debuginfod", class_run, - _("Set debuginfod options"), - _("Show debuginfod options"), + _("Set debuginfod options."), + _("Show debuginfod options."), &set_debuginfod_prefix_list, &show_debuginfod_prefix_list, &setlist, &showlist);
reply other threads:[~2021-10-31 17:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211031173516.F061B3857413@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).