public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/doc: reword description of DisassembleInfo.read_memory Date: Mon, 24 Oct 2022 17:46:09 +0000 (GMT) [thread overview] Message-ID: <20221024174609.8B0FC3857B9A@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c6d20401a20148b032cb7fb9dba079466a9383cc commit c6d20401a20148b032cb7fb9dba079466a9383cc Author: Andrew Burgess <aburgess@redhat.com> Date: Mon Oct 24 18:04:42 2022 +0100 gdb/doc: reword description of DisassembleInfo.read_memory While reading the documentation of DisassembleInfo.read_memory I spotted the word 'available' in one sentence where it didn't make sense. Diff: --- 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 @@ bytes it has available, in this case @code{builtin_disassemble} will 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
reply other threads:[~2022-10-24 17:46 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=20221024174609.8B0FC3857B9A@sourceware.org \ --to=aburgess@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).