diff options
author | Andrew Burgess <aburgess@redhat.com> | 2022-10-24 18:04:42 +0100 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2022-10-24 18:04:42 +0100 |
commit | c6d20401a20148b032cb7fb9dba079466a9383cc (patch) | |
tree | e0d8fc7ffc1a3be02b56a43db6fba18490e90038 /gdb | |
parent | 1be79b1ebfad75626bf86eee35839e0afd081fdd (diff) | |
download | gdb-c6d20401a20148b032cb7fb9dba079466a9383cc.zip gdb-c6d20401a20148b032cb7fb9dba079466a9383cc.tar.gz gdb-c6d20401a20148b032cb7fb9dba079466a9383cc.tar.bz2 |
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.
Diffstat (limited to 'gdb')
-rw-r--r-- | gdb/doc/python.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi index f73b9a4..e7adeac 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 |