public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Fix some spelling errors. Date: Thu, 16 Jan 2020 23:47:00 -0000 [thread overview] Message-ID: <40c940992759aba79013a2c590c29f03ea754e77@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 40c940992759aba79013a2c590c29f03ea754e77 *** commit 40c940992759aba79013a2c590c29f03ea754e77 Author: Christian Biesinger <cbiesinger@google.com> AuthorDate: Thu Jan 16 16:41:53 2020 -0600 Commit: Christian Biesinger <cbiesinger@google.com> CommitDate: Thu Jan 16 16:46:25 2020 -0600 Fix some spelling errors. I noticed those from a lintian run: https://salsa.debian.org/cbiesinger-guest/gdb/-/jobs/514119 gdb/ChangeLog: 2020-01-16 Christian Biesinger <cbiesinger@google.com> * btrace.c (btrace_compute_ftrace_1): Fix spelling error (Unkown). (btrace_stitch_trace): Likewise. * charset.c (intermediate_encoding): Likewise (vaild). * nat/linux-btrace.c (linux_read_pt): Likewise (Unkown). * python/py-record-btrace.c (struct PyMethodDef): Likewise (occurences). * record-btrace.c (record_btrace_print_conf): Likewise (unkown). gdb/testsuite/ChangeLog: 2020-01-16 Christian Biesinger <cbiesinger@google.com> * lib/gdb.exp: Fix spelling error (seperatelly). Change-Id: I2a44936bac295020f217fb6c78b99b0a8d09cf9a diff --git a/gdb/ChangeLog b/gdb/ChangeLog index cc3a43cf2d..5301385ecb 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,12 @@ +2020-01-16 Christian Biesinger <cbiesinger@google.com> + + * btrace.c (btrace_compute_ftrace_1): Fix spelling error (Unkown). + (btrace_stitch_trace): Likewise. + * charset.c (intermediate_encoding): Likewise (vaild). + * nat/linux-btrace.c (linux_read_pt): Likewise (Unkown). + * python/py-record-btrace.c (struct PyMethodDef): Likewise (occurences). + * record-btrace.c (record_btrace_print_conf): Likewise (unkown). + 2020-01-16 Hannes Domani <ssbssa@yahoo.de> * windows-tdep.c (windows_get_tlb_type): diff --git a/gdb/btrace.c b/gdb/btrace.c index 0c7becd349..bbf8749649 100644 --- a/gdb/btrace.c +++ b/gdb/btrace.c @@ -1533,7 +1533,7 @@ btrace_compute_ftrace_1 (struct thread_info *tp, return; } - internal_error (__FILE__, __LINE__, _("Unkown branch trace format.")); + internal_error (__FILE__, __LINE__, _("Unknown branch trace format.")); } static void @@ -1791,7 +1791,7 @@ btrace_stitch_trace (struct btrace_data *btrace, struct thread_info *tp) return -1; } - internal_error (__FILE__, __LINE__, _("Unkown branch trace format.")); + internal_error (__FILE__, __LINE__, _("Unknown branch trace format.")); } /* Clear the branch trace histories in BTINFO. */ diff --git a/gdb/charset.c b/gdb/charset.c index 480ed366a4..5cfd2d8030 100644 --- a/gdb/charset.c +++ b/gdb/charset.c @@ -989,7 +989,7 @@ intermediate_encoding (void) /* Not valid, free the allocated memory. */ xfree (result); /* No valid charset found, generate error here. */ - error (_("Unable to find a vaild charset for string conversions")); + error (_("Unable to find a valid charset for string conversions")); } #endif /* USE_INTERMEDIATE_ENCODING_FUNCTION */ diff --git a/gdb/nat/linux-btrace.c b/gdb/nat/linux-btrace.c index 03fc85e2ec..e972a07227 100644 --- a/gdb/nat/linux-btrace.c +++ b/gdb/nat/linux-btrace.c @@ -889,7 +889,7 @@ linux_read_pt (struct btrace_data_pt *btrace, return BTRACE_ERR_NONE; } - internal_error (__FILE__, __LINE__, _("Unkown btrace read type.")); + internal_error (__FILE__, __LINE__, _("Unknown btrace read type.")); } /* See linux-btrace.h. */ diff --git a/gdb/python/py-record-btrace.c b/gdb/python/py-record-btrace.c index a3c3a546d7..08613a856d 100644 --- a/gdb/python/py-record-btrace.c +++ b/gdb/python/py-record-btrace.c @@ -808,7 +808,7 @@ recpy_bt_goto (PyObject *self, PyObject *args) struct PyMethodDef btpy_list_methods[] = { - { "count", btpy_list_count, METH_O, "count number of occurences"}, + { "count", btpy_list_count, METH_O, "count number of occurrences"}, { "index", btpy_list_index, METH_O, "index of entry"}, {NULL} }; diff --git a/gdb/record-btrace.c b/gdb/record-btrace.c index 33ee4e9d81..619ecde025 100644 --- a/gdb/record-btrace.c +++ b/gdb/record-btrace.c @@ -541,7 +541,7 @@ record_btrace_print_conf (const struct btrace_config *conf) return; } - internal_error (__FILE__, __LINE__, _("Unkown branch trace format.")); + internal_error (__FILE__, __LINE__, _("Unknown branch trace format.")); } /* The info_record method of target record-btrace. */ diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index c35afbd13f..c4a760ef51 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,7 @@ +2020-01-16 Christian Biesinger <cbiesinger@google.com> + + * lib/gdb.exp: Fix spelling error (seperatelly). + 2020-01-14 Tom Tromey <tom@tromey.com> PR symtab/12535: diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index cb5a3f7aea..2d230b791e 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -3877,7 +3877,7 @@ proc gdb_compile {source dest type options} { # Force output to unbuffered mode, by linking in an object file # with a global contructor that calls setvbuf. # - # Compile the special object seperatelly for two reasons: + # Compile the special object separately for two reasons: # 1) Insulate it from $options. # 2) Avoid compiling it for every gdb_compile invocation, # which is time consuming, especially if we're remote
next reply other threads:[~2020-01-16 23:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-16 23:47 gdb-buildbot [this message] 2020-01-16 23:38 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, branch master gdb-buildbot 2020-01-17 16:36 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** gdb-buildbot 2020-01-17 17:24 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master gdb-buildbot 2020-01-17 17:24 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2020-01-17 17:40 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
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=40c940992759aba79013a2c590c29f03ea754e77@gdb-build \ --to=gdb-buildbot@sergiodj.net \ --cc=gdb-testers@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).