From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH] gdb/doc: reword description of DisassembleInfo.read_memory
Date: Mon, 24 Oct 2022 18:06:20 +0100 [thread overview]
Message-ID: <20221024170620.2910797-1-aburgess@redhat.com> (raw)
While reading the documentation of DisassembleInfo.read_memory I
spotted the word 'available' in one sentence where it didn't make
sense.
---
gdb/doc/python.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index f73b9a43a86..e7adeacffd1 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -6812,7 +6812,7 @@
not itself raise a @code{MemoryError}.
Any other exception type raised in @code{read_memory} will propagate
-back and be available re-raised by @code{builtin_disassemble}.
+back and be re-raised by @code{builtin_disassemble}.
@end defun
@end deftp
--
2.25.4
next reply other threads:[~2022-10-24 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 17:06 Andrew Burgess [this message]
2022-10-24 17:11 ` Eli Zaretskii
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=20221024170620.2910797-1-aburgess@redhat.com \
--to=aburgess@redhat.com \
--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).