aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-breakpoint.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2025-04-22 17:32:53 +0100
committerAndrew Burgess <aburgess@redhat.com>2025-04-22 17:40:12 +0100
commit4183b1e3a2f36dd67e25dff4be642c48bf214d64 (patch)
tree23bae369b8ff357ccf9a2e52de9d64d59175b08b /gdb/python/py-breakpoint.c
parent5d4187339f9f2f338d540adbdfd174aa9f1e92ab (diff)
downloadbinutils-4183b1e3a2f36dd67e25dff4be642c48bf214d64.zip
binutils-4183b1e3a2f36dd67e25dff4be642c48bf214d64.tar.gz
binutils-4183b1e3a2f36dd67e25dff4be642c48bf214d64.tar.bz2
gdb/doc: use @samp{} in Python docs
In this review: https://inbox.sourceware.org/gdb-patches/86sem6ase5.fsf@gnu.org it was pointed out that I should use @samp{} around some text I was adding to the documentation. However, the offending snippet of documentation was something I copied from elsewhere in python.texi. This commit fixes the original to use @samp{}.
Diffstat (limited to 'gdb/python/py-breakpoint.c')
0 files changed, 0 insertions, 0 deletions