From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 08/10] [gdb/python] Fix doc string of valpy_const_value
Date: Fri, 2 Jun 2023 17:56:37 +0200 [thread overview]
Message-ID: <20230602155639.28245-9-tdevries@suse.de> (raw)
In-Reply-To: <20230602155639.28245-1-tdevries@suse.de>
In gdb/python/py-value.c, in the value_object_methods array I noticed:
...
{ "const_value", valpy_const_value, METH_NOARGS,
"Return a 'const' qualied version of the same value." },
...
Fix the qualied -> qualified typo.
---
gdb/python/py-value.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/python/py-value.c b/gdb/python/py-value.c
index 6c62820c63b..a3d80adce03 100644
--- a/gdb/python/py-value.c
+++ b/gdb/python/py-value.c
@@ -2106,7 +2106,7 @@ reinterpret_cast operator."
{ "rvalue_reference_value", valpy_rvalue_reference_value, METH_NOARGS,
"Return a value of type TYPE_CODE_RVALUE_REF referencing this value." },
{ "const_value", valpy_const_value, METH_NOARGS,
- "Return a 'const' qualied version of the same value." },
+ "Return a 'const' qualified version of the same value." },
{ "lazy_string", (PyCFunction) valpy_lazy_string,
METH_VARARGS | METH_KEYWORDS,
"lazy_string ([encoding] [, length]) -> lazy_string\n\
--
2.35.3
next prev parent reply other threads:[~2023-06-02 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 15:56 [PATCH 00/10] [gdb] Fix typos and misspellings Tom de Vries
2023-06-02 15:56 ` [PATCH 01/10] [gdb/ada] Fix argument name misspelling Tom de Vries
2023-06-02 15:56 ` [PATCH 02/10] [gdbserver] Fix typo in debug message Tom de Vries
2023-06-02 15:56 ` [PATCH 03/10] [gdb/compile] " Tom de Vries
2023-06-02 15:56 ` [PATCH 04/10] [gdb/cli] Fix help text of maint set ignore-prologue-end-flag Tom de Vries
2023-06-02 15:56 ` [PATCH 05/10] [gdb/cli] Fix help text of maint info target-sections Tom de Vries
2023-06-02 15:56 ` [PATCH 06/10] [gdb/tui] Fix help text of show tui tab-width Tom de Vries
2023-06-02 15:56 ` [PATCH 07/10] [gdb/guile] Fix doc string for value-optimized-out? Tom de Vries
2023-06-02 15:56 ` Tom de Vries [this message]
2023-06-02 15:56 ` [PATCH 09/10] [gdb/tdep] Fix typo in debug message Tom de Vries
2023-06-02 15:56 ` [PATCH 10/10] [gdb] Fix typos Tom de Vries
2023-06-02 17:04 ` [PATCH 00/10] [gdb] Fix typos and misspellings Tom Tromey
2023-06-03 10:19 ` Tom de Vries
2023-06-03 15:28 ` Tom Tromey
2023-06-05 7:20 ` Bruno Larsen
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=20230602155639.28245-9-tdevries@suse.de \
--to=tdevries@suse.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).